Build an automation with Trigger, API Request, Webhook, and Transform

Use the four automation building blocks as separate jobs: start a run, call an API, notify an external endpoint, and reshape data between steps.

Where: Flowgen → Add → Automation

Key ideas

• Trigger starts the run: Manual and schedule triggers can be authored on canvas; inbound webhook and HTTP-route identities are minted when the flow is published.
• API Request reads or writes a service: It owns methods, typed template variables, bodies, response parsing, saved connection references, limits, retries, and idempotency.
• Send Webhook delivers an event: It sends a bounded payload to a target with delivery history, retry controls, and optional platform signing.
• Extract / Merge reshapes values: Use the Transform node between external schemas and your flow instead of hiding parsing in prompts.

Steps

1. Add a Trigger and declare the values the rest of the flow expects.
2. Transform the incoming payload into stable named fields.
3. Call an API or generate content, then map the result into the destination contract.
4. Send a webhook when needed, test safe paths on canvas, publish the automation, and inspect run/delivery history.

Limitations and important notes

• A canvas test cannot fake a signed inbound webhook delivery or an authenticated HTTP-route subject.
• Credentials belong in saved connections or platform signing, not in user-authored headers or wired values.

Related guides

• Start an automation with the Trigger node
• Call an external API with API Request
• Notify another service with Send Webhook
• Extract / Merge: take apart, combine, and type connected values
• Publish and manage Flowgen automations