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 with the incoming intent and explicit filters.
  2. Apply a deterministic selection rule or pause for review.
  3. Start an Action with the exact capability revision and a stable request ID.
  4. Store actionId and poll or schedule a later status check.
Do not automatically approve a changed price, payload, merchant, or provider. Route approval-required states to a human review step.

​
Map the durable fields

Use Delay or a later Zap for polling instead of holding one run open indefinitely. Keep the same Action ID across every continuation.
Last modified on September 22, 2026