HTTP request · Activation · One request per record; continues on success
Sends each record to any URL you choose — a webhook, an internal API, or a third-party tool. Unlike most activation steps, records continue afterward, so it can sit mid-workflow or at the end.
When to use it
Use it to connect a workflow to anything Ocean doesn't integrate with directly: push to a custom endpoint, trigger a Zapier hook, or notify an internal service.
What it does
For each record, it fires one HTTP request to your URL. On a success response, the record passes through unchanged so later steps can keep going. On a failure, that record is recorded as failed and dropped, without affecting the others.
Configure it
URL — where to send the request.
Method — GET, POST, and so on.
Headers — including any auth headers. Secret header values are stored encrypted and hidden after you save them.
Body — the payload. Type
@to build the URL, headers, and body from record fields.Save from response — optionally pull fields out of the JSON response and save them as columns on each record, so later steps can use them. Give each one a name and a JSON path (like
data.emailoritems[0].id; leave the path empty to save the whole body). Leave this empty to just send and move on. Use Test request to send once and click the response fields to map them.
Cost
No credit cost. See Credits in workflows.
Gotchas
A non-success response drops that record and notes the failure in Activity — check there if records aren't continuing.
Because it can pass records through, you can chain steps after it — but only records that got a success response continue.