To build a highly robust, enterprise-grade human-in-the-loop workflow, you should avoid attempting to “pause” or delay a single scenario run (which will hit execution timeouts and waste operations).
The optimal architectural pattern is to split this into two asynchronous scenarios connected by a database (such as Airtable or a Make Data Store) and a Webhook.
Here is how you structure this pattern:
Scenario 1: Intake, Hold & Notify (The “Pause”)
This scenario handles the initial request and halts the automated flow until a human acts.
- Trigger: New Form Submission (Form / request enters).
- Action: Create Record (Airtable / Make Data Store)
- Store all request details.
- Set a field called “Status” to: Pending Review.
- Action: Generate Review Action Link
- If using Airtable, you can use an Airtable Interface with an “Approve” button that triggers a webhook.
- Alternatively, generate a custom webhook URL that includes the Record ID as a parameter (e.g., https://hook.make.com/your-webhook-id?recordId={{Airtable_Record_ID}}).
- Action: Send Notification (Slack / Email)
- Notify the designer with the request details and the active Review Link.
At this point, Scenario 1 terminates. No operations are wasted, and there are no timeout risks.
Scenario 2: Action & Release (The “Resume”)
This scenario triggers only when the human designer explicitly approves the draft.
- Trigger: Custom Webhook (Instant)
- Triggers when the designer clicks “Approve” in your review tool or updates the status in Airtable, passing the original Record ID.
- Action: Get Record (Airtable / Make Data Store)
- Fetch the original request details using the Record ID passed from the webhook.
- Action: Continue Workflow
- Resume the automation (e.g., trigger the final AI video rendering, notify the client, update the database status to “Approved”).
Why this pattern is optimal:
- Zero Timeout Risk: The human reviewer can take 10 minutes or 10 days; the system will never time out.
- Operation Cost: No operations are consumed while the system is “waiting.”
- Reliable State Machine: You maintain a permanent audit trail of your creative requests and their current statuses in your database.