HTTP request · Activation · One request per record; records continue afterward
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. It's also how you pull data in from your own systems — send the request, then read the reply with Parse JSON.
What it does
For each record, it fires one HTTP request to your URL and saves two fields on the record: Status code and Response body. The record then continues to the next step.
To use anything inside the response, follow this step with Parse JSON and point it at the response body — that's what turns the raw reply into fields later steps can read.
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.Fail on error response — on by default, so a 4xx or 5xx marks that record failed. Turn it off to let those records carry on with the status code and response body intact, which is what you want if you plan to branch on the result rather than treat it as an error.
Cost
No credit cost. See Credits in workflows.
Gotchas
The response body arrives as raw text. Add Parse JSON after this step to read fields out of it.
With Fail on error response on, a non-success reply marks the record failed and it goes no further — check Activity if records aren't continuing.
To keep going even when a request genuinely fails, turn on Continue on failure. See Troubleshooting workflows.