
Ocean.io webhooks
If it can receive a request, it can receive Ocean's accounts.
Point Ocean at any URL and companies and contacts arrive there. A webhook export is the quick send, and an HTTP request step inside a workflow gives full control over the URL, headers and body. It is the fastest way to reach a tool with no native integration.
What lands in Webhooks
- Companies and contacts, sent to the URL you choose
- Your own headers, including secret ones
- A body you shape with fields from earlier steps
Who it's for
- RevOps: connect any tool without an engineer
- Marketing: send ranked lists to the tools campaigns run in
How it works
- Create a receiving URL in your tool
- Add it as a webhook in Ocean, or as an HTTP request step in a workflow
- Send a segment and route it onward
Under the hood
- Webhook export is switched on per organization. Ask us to enable it.
- The HTTP request step templates the URL, headers and body per record. Secret header values are stored encrypted.
- Ocean checks every destination before sending and refuses internal or private addresses.
- You can cap requests per window, and a failed request is retried once.
Frequently asked questions
Does Ocean.io integrate with Webhooks?
Yes. Webhooks are part of Ocean: add a URL as a webhook export or an HTTP request step.
Can I use webhooks with Zapier or n8n?
Yes. Point an Ocean webhook at a Zapier Catch Hook or an n8n webhook trigger, then route accounts and contacts to any of the apps those tools support. It is the fastest way to connect a tool that has no native Ocean integration.
Is it safe to point Ocean at my own endpoint?
Yes. Ocean validates every destination before it sends and refuses internal or private addresses. Secret header values are stored encrypted. You can cap how many requests go out per window, and a failed request is retried once before it is reported.
A worked example (illustrative)
Every Monday the workflow sends new Tier 1 companies to different internal endpoints by region. DACH goes to one team's intake, the Nordics to another, and each message carries the reason and the owner's email. Nobody triages a shared list.
- Recommendations step: this week's new Tier 1 companies.
- Route by headquarter country: DACH, Nordics or the rest.
- HTTP request to each team's endpoint, with a secret header.
- Rate cap per window, and a retry on failure.
Related integrations
Put Ocean to work in your stack
- Ranked accounts and the reason each one fits
- Scores, segments and signals written to the fields you choose