Make a policy-bounded HTTP call with typed template variables, connection-based auth, response parsing, retries, and idempotency controls.
Where: Flowgen → Add → Automation → API Request
Key ideas
- Explicit request contract: Choose GET, HEAD, POST, PUT, PATCH, or DELETE; define URL variables with string/number/boolean types, defaults, required flags, and secret redaction.
- Bodies and responses: Write methods can send no body, JSON, form fields, or text. Responses can be parsed automatically, forced to structured data, or kept as plain text.
- Safe transport controls: Auth is referenced through a saved connection. Credential, platform-signature, and transport-owned headers are refused rather than sent.
- Bounded retries: Timeout/size controls can only lower platform policy limits. Retry count, backoff, Retry-After handling, and idempotency govern repeat attempts.
- API Request card: HttpRequestNode uses the generic shared-card path. Perform a policy-bounded HTTP request with typed variables, safe auth, response parsing, limits, retries, and idempotency.
- Properties sidebar: automationNodes.tsx
- Opened surfaces: Structured/result preview
Steps
- Choose the HTTP method and enter a URL template.
- Declare every template variable, query parameter, allowed custom header, and body field; reference a saved connection for authentication.
- Choose response parsing and set smaller timeout/size limits only when useful.
- For write methods, confirm the target supports idempotency before enabling retries; run and inspect status, headers, body, duration, and redacted errors.
API Request controls and presets
- Add path: Flowgen → Add → Automation → API Request.
- Card: HttpRequestNode.
- Properties: automationNodes.tsx.
- Controls: Method; URL variables; query/headers/body; response mode; connection; timeout/size; retry/backoff; idempotency.
- Opened surfaces: Structured/result preview.
Tips
- Use Transform before the request to create a stable external schema.
- Test with a safe endpoint or non-production account before allowing an automation to write.
Limitations and important notes
- URL, response size, content type, timeout, egress, and header rules are enforced by platform policy.
- Unsafe POST/PATCH requests are not automatically retry-safe unless an idempotency key is actually supported and sent.
Troubleshooting
A header is rejected
Move credentials to a saved connection and remove authorization, cookie, host, content-length, x-f0 signature, or other transport/platform-owned headers.