Use a protected HTTP or code node to call Darwin. Keep Search as a read-only discovery step and represent each Action mutation as a separate, reviewable step.
Prefer Gumloop’s MCP connection UI and follow the public reusable-node recipe so tools are discovered dynamically.
Preserve canonical result order and the selected capability revision. Store actionId so the flow can resume after waiting for a person, a provider connection, or a payment interaction.
Do not place API keys, provider tokens, or payment data in prompts, visible node labels, run logs, or generated output.
Flow checkpoints
Do not hold one flow open indefinitely. Resume from durable state and call Get action before choosing the next node. Last modified on September 22, 2026
