Start with an agent that can invoke an approved automation and a workflow owner who controls its request store and notification route. Use this when the customer’s job lasts longer than a tool call, such as an employee approval or a support callback.

Define what the receipt confirms

A saved pending receipt needs a request reference, an explicit state and a way for the requester to get the eventual outcome. Have the workflow owner save that record before returning the receipt and deduplicate its stable request ID. A reference to a queued job is not proof its downstream operation succeeded.

For a concrete approval flow, use Power Automate’s protected HTTP trigger and approval receipt. Start a Zap has a different contract: Catch Hook returns a transport acknowledgment before downstream Zap work, and that response cannot be customized. Say the request was submitted for processing. Retain the application-supplied request ID for Zap History and destination reconciliation; the acknowledgment does not establish that a durable work record exists.

Return the receipt in the conversation

1

Obtain the workflow handoff

For a saved receipt, obtain its tested schema, saved reference and customer notification or status route. For Catch Hook, obtain the submitted request ID and the owner’s route for checking the Zap and destination. In either case, ask the owner to prove a duplicate submission does not create duplicate work. For approvals, verify that the intended approver sees the request and the requester receives the eventual result.

2

Keep acknowledgment visible to the agent

For an API tool, open its attached settings and keep Async execution off for this initial request. This lets the agent inspect the HTTP acknowledgment during the turn; the external workflow can continue afterward. A background tool setting and a provider’s pending job are different execution choices.

3

Write a truthful answer rule

In the attached tool’s Trigger and agent instructions, say when to submit and how to interpret its result. Use this pattern with the workflow’s actual fields and existing completion route:

4

Test receipt and eventual completion separately

In the isolated project’s Run, submit the safe test request and inspect the current response and agent answer. For a saved receipt, find that record in the provider and complete its later action. For Catch Hook, match the submitted request ID to Zap History and the destination record. Verify the final notification reaches the intended person. Test rejection as well as approval, and repeat the same request ID to check duplicate handling.

Handle an unknown outcome

If the call times out, tell the requester its outcome could not be confirmed and retain the stable request ID for investigation. A timeout does not cancel a Make scenario, Zap or other external job. Follow Investigate a failed automation before replaying a write.

An external completion event does not automatically resume a closed Voiceflow conversation. Keep the verified notification in the provider/application, or separately implement and test a status lookup in the existing customer channel before promising it in the agent’s answer.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.