Skip to main content
Use Zapier’s HTTP or code steps to call Darwin from a trusted automation environment. Keep the API key in Zapier’s protected connection or secret storage, not in visible step input.
Private integration testing is the current path. Darwin is not yet listed in Zapier’s App Directory; public listing requires a production integration, real users, reviewer access, and Zapier review.

​
Workflow shape

1

Search and select

Search with the incoming query and optional category or objective. Use the first ready ranked capability by default, or apply a deterministic rule or human review.Success: the Zap holds one exact agent and capability ID.
2

Start and persist a thread

Call start_thread with the selected result’s agent as targetAgent, plus messageType and messageContent; optionally set agent, capability, and one stable idempotencyKey. Store the returned thread and cursor, then continue with send_message.Success: the Zap has a durable handle instead of relying on one run’s transient output.
3

Resume from state

Use Delay or a later Zap to call get_thread with the last consumed cursor. Branch only from typed events and operation states.Success: waits and human reviews resume the same work without creating duplicates.
Do not automatically approve a changed price, payload, merchant, or provider. Route approval-required states to a human review step.

​
Map the durable fields

Keep the same thread ID across every continuation.
Last modified on October 4, 2026