Skip to main content
Use an HTTP Request or code node for Darwin’s REST API. Store credentials in n8n credentials and Action identifiers in workflow data. For dynamic MCP tool discovery, import the credential-free Darwin MCP workflow, then attach your own n8n model and MCP OAuth credentials. The public template is self-serve; verification of a future native Darwin node is a separate reviewed process.
The workflow template works now. A native verified Darwin node is not yet listed and requires an npm package with provenance plus n8n Creator Portal review.
Branch on Darwin’s structured status:
  • continue polling for running
  • wait for input on awaiting_user
  • send an explicit review for approval_required
  • open a first-party Darwin link for connection or payment
  • finish only on completed or stopped
Configure retries to preserve the same requestId for the same logical mutation.

​
Suggested node sequence

Use n8n’s wait-and-resume behavior for human input and first-party browser interactions. Before any mutation after the wait, read the current Action again so stale workflow data cannot override a newer state.
Last modified on September 22, 2026