Ocean.io can connect with Nango for routing Ocean's accounts and contacts into other tools through Nango
Connect today

Nango integration with Ocean.io

If Nango can receive a request, it can receive Ocean's accounts.

Most teams need Ocean's output in a tool Ocean has no connector for. A webhook solves that: point it at a trigger in Nango and each company arrives as an event, ready to be routed, enriched or turned into a task.

Ways to connect Nango

Route Status What it does
Webhook export Works today Send companies and contacts from Ocean to Nango's inbound webhook, or to any URL that accepts a POST. Switched on per organization.
HTTP request step Works today A workflow step calls Nango's REST API with your own API key, kept in an encrypted header. Ocean fills the URL and body per record, caps requests per window and retries a failure once.
Ocean API Works today Search, enrichment, lookalikes, segments and exclusion lists from your own code or pipeline, authenticated with an API token.

What lands in Nango

  • Companies and contacts, delivered to a Nango trigger
  • Any field a workflow has, including tier and matched signals

Who it's for

  • RevOps: connect any tool without an engineer
  • Marketing: ranked lists in the tools campaigns run in

Ocean acts as a context layer on Nango

Run Ocean's MCP server and Nango's on one agent. Ocean supplies the accounts. Nango runs what happens next.

Ocean Company and people search, lookalikes, segments, fit scores and buying committees
MCP Any AI agent that supports MCP carries the context across
Nango Receives it and acts
Sample prompt
“Ask Ocean for new Tier 1 accounts, then trigger the Nango workflow that creates the follow-up tasks.”

The agent reaches Nango through an automation tool's MCP server or its API. Searches and exports spend Ocean credits.

Frequently asked questions

  • Does Ocean.io integrate with Nango?

    Yes, through a webhook export, an HTTP request step and the Ocean API. Over MCP, an agent reaches Nango through an automation tool's MCP server or Nango's API.

  • What does an Ocean app in Nango add?

    A trigger for new ranked accounts and actions for search and enrichment, in the app picker. Today the webhook and the HTTP request step cover the same ground with a little more setup.

A worked example (illustrative)

A new Tier 1 company arrives in Nango. The flow looks up the owner for its region, creates a task with the reason the company fits, and posts it to the team channel. Territory rules live in Nango, so they change without touching Ocean.

  1. Ocean webhook: a new Tier 1 company arrives.
  2. Look up the owner for the company's region.
  3. Create a task with the reason it fits.
  4. Post it to the team channel.

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