Notify another service with Send Webhook

Deliver a bounded POST, PUT, or PATCH payload with safe custom headers, optional platform signing, and one traceable delivery history across retries.

Where: Flowgen → Add → Automation → Send Webhook

Key ideas

Delivery rather than general API browsing: Send Webhook is for notifying an endpoint with an event payload. Use API Request when you need broader request/response and connection behavior.
One logical delivery: Retries append attempts to the same derived delivery identity instead of creating independent duplicate delivery records.
Platform signing: Optional signing is performed by the platform; user headers cannot forge the x-f0 signature namespace or provide raw authorization credentials.
Send Webhook card: OutboundWebhookNode uses the generic shared-card path. Deliver a bounded POST/PUT/PATCH event payload with safe headers, retries, optional platform signing, and delivery history.
Properties sidebar: automationNodes.tsx
Opened surfaces: Structured/result preview

Connect or enter the payload, add the destination URL, and choose POST, PUT, or PATCH.
Add only safe custom headers and set the content type.
Set attempts and lower timeout/body limits when appropriate; enable signing only when the receiver verifies the platform signature.
Run and inspect the delivery/response outputs, including each attempt and the final redacted response excerpt.

Add path: Flowgen → Add → Automation → Send Webhook.
Card: OutboundWebhookNode.
Properties: automationNodes.tsx.
Controls: URL; method; payload; headers/content type; attempts; timeout/size; signing.
Opened surfaces: Structured/result preview.

Design the receiver to deduplicate by the delivered identity or idempotency information.
Use Transform to make the outgoing payload contract explicit.

User headers cannot set authorization, cookies, host/length/transfer headers, idempotency-key, content-type, or the x-f0 namespace.
Request and response bodies are bounded; delivery history keeps only a limited response excerpt.

Confirm the receiving service deduplicates the delivery and that the workflow is not independently issuing multiple logical webhook steps.