Recipe
Make Lead Follow-up
Record a Make scenario that receives a lead, prepares a follow-up, and keeps a readable receipt of the result.
Record the handoff, not the whole scenario
Use this recipe when Make prepares a follow-up task, draft response, or sales handoff and you want a clear receipt before the next action happens.
When to use this recipe
Lead capture
A form, CRM, spreadsheet, or ad platform sends a new lead into a Make scenario.
Draft follow-up
Make prepares a task, message draft, or internal note for a person to review.
Sales handoff
The receipt records who should follow up, what was prepared, and what still needs attention.
Optional review
Use review fields when the draft should be checked before a message is sent or a CRM record is changed.
Workflow shape
Lead received
A trigger module receives or finds the new lead.
Context gathered
Make enriches, classifies, or formats the lead details.
Draft prepared
A task, note, or response draft is prepared.
Receipt created
The HTTP module sends one JSON request to Automation Receipts.
Follow-up logged
A later event can record whether the task was completed or held.
Request settings
- Module
- HTTP > Make a request
- Method
POST- URL
https://automationreceipts.com/api/v1/runs- Body type
- Raw JSON or JSON data structure
- Headers
- Authorization and Content-Type
Headers
Authorization: Bearer aar_live_REPLACE_ME
Content-Type: application/jsonExample run payload
Send this payload to POST https://automationreceipts.com/api/v1/runs. Replace example values with mapped values from Make when the workflow is ready.
Create Make lead receipt
{
"automation_name": "Make Lead Follow-up",
"run_uid": "make-lead-REPLACE_WITH_EXECUTION_ID",
"source_type": "make",
"trigger_type": "new_lead",
"status": "needs_review",
"risk_level": "medium",
"input_summary": "A new lead requested pricing information from the website form.",
"output_summary": "Make prepared a follow-up task and a draft response for review.",
"tools_used": "Make scenario, CRM module, email draft step",
"approval_required": true,
"approval_status": "pending",
"final_action": "Draft held for review before sending.",
"events": [
{
"event_type": "trigger_received",
"event_label": "Lead received",
"event_summary": "The scenario started from a new website lead."
},
{
"event_type": "output_generated",
"event_label": "Follow-up drafted",
"event_summary": "Make prepared the follow-up task and response draft."
},
{
"event_type": "approval_requested",
"event_label": "Review requested",
"event_summary": "The follow-up draft is waiting for review."
}
]
}Make run_uid unique
Map a Make execution ID, generated UUID, timestamp, or source lead ID plus timestamp into run_uid. Automation Receipts rejects duplicate run_uid values within the same workspace.
Events this recipe uses
| Event type | Label | What it records |
|---|---|---|
trigger_received |
Lead received | The Make scenario started from a lead source. |
output_generated |
Follow-up drafted | The scenario prepared the task, note, or draft response. |
approval_requested |
Review requested | A person should check the draft before the final action. |
action_taken |
Follow-up sent or task completed | The later outcome was recorded on the same receipt. |
Append the final action
If the workflow continues after the receipt is created, append a timeline event using the original run_uid.
Append event request
curl -X POST "https://automationreceipts.com/api/v1/runs/make-lead-REPLACE_WITH_EXECUTION_ID/events" \
-H "Authorization: Bearer aar_live_REPLACE_ME" \
-H "Content-Type: application/json" \
-d '{
"event_type": "action_taken",
"event_label": "Follow-up task completed",
"event_summary": "The reviewed follow-up task was completed in the CRM."
}'Make notes
Place the HTTP module late
Create the receipt after Make has the lead details, draft summary, review state, and final action.
Use mapped values carefully
Hardcoded summaries are fine for a controlled run. Use mapped lead and scenario values before enabling the live scenario.
Keep the receipt readable
Do not send full form payloads, private notes, CRM exports, or raw email bodies unless the reader needs them.
Use review only when useful
If the scenario can safely create a task without review, set approval_required to false and approval_status to not_required.
Review and data notes
| Workflow state | Suggested fields |
|---|---|
| No review needed | approval_required: false, approval_status: "not_required" |
| Waiting for review | status: "needs_review", approval_required: true, approval_status: "pending" |
| Reviewed elsewhere | approval_status can record the outcome even when review happened in another tool. |
Send concise summaries by default. Avoid raw messages, documents, secrets, API keys, and full model payloads unless the receipt reader truly needs that information.
Troubleshooting
| Problem | What it usually means | Fix |
|---|---|---|
| 401 unauthorized | The bearer token is missing, wrong, or revoked. | Use the full active API key in the Authorization header. |
| 409 duplicate run_uid | A receipt already exists with that run ID in the workspace. | Map a dynamic value into run_uid for each workflow run. |
| 422 validation error | A required field is missing or a machine value is not allowed. | Check automation_name, run_uid, summaries, source_type, status, and approval_status. |
| Make sends text instead of JSON | The HTTP module body type or headers are not set for JSON. | Use application/json and send a JSON object body. |
| Same receipt appears as duplicate | The scenario reused the same run_uid on a later execution. | Map a changing execution ID, UUID, or timestamp into run_uid. |