API call
The API call step sends an HTTP request (GET, POST, PUT, PATCH, DELETE) for each record. Use it to notify a CRM, fetch extra data, or write results back to another system.
Typical setup
Section titled “Typical setup”- Choose method and URL.
- Choose authentication (none, bearer, basic, or custom header).
- Point tokens at the Vault or a prior step field when possible.
- Choose what body to send (full record, payload only, or none).
“Payload only” sends metadata fields — the same set that entered the pipeline.
- Prefer HTTPS endpoints.
- Do not log full authorization headers.
- Test with one row before a large run.