← All selected work

FUNCTIONAL DEMONSTRATION

One inquiry. Every follow-up accounted for.

A connected lead intake workflow that turns a form response into a record, a team alert, an acknowledgment, and a task.

The handoff problem

A new inquiry can involve copying details into a tracker, notifying a colleague, replying to the sender, and assigning a task. Each manual handoff adds another opportunity to miss a step.

What I built

Google Forms responses enter a raw response sheet. Make watches for new rows, writes a structured lead record, posts a Slack notification, sends a Gmail acknowledgment, and creates a ClickUp task.

A problem solved during the build

The Gmail module initially returned an insufficient authentication scopes error. Reconnecting with the required send permission resolved it. The documented workflow also includes email-format validation and a ClickUp retry handler.

Estimated impact

At an assumed 100 leads per month and 10–15 minutes of manual handling per lead, the modeled capacity gain is 16.7–25 hours per month. This is a projection, not measured client savings. End-to-end response time depends on the configured trigger schedule and successful downstream steps.

Actual Make scenario connecting the workflow steps.
Actual Make scenario connecting the workflow steps.
Example follow-up task created in ClickUp.
Example follow-up task created in ClickUp.
← Back to selected workDiscuss your workflow ↗