Resources · n8n integration

Mocean n8n integrationAutomate Mocean with n8n.

Mocean sits at the point in a workflow where a message has to leave the building. The Mocean n8n integration exposes 2 operations across 2 resources, SMS and Voice, both built on the same three required fields. No trigger node ships with it, so the run always starts somewhere else.

Try the Mocean integration on n8nSee the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Mocean n8n integration actually give you?

The Mocean n8n integration wires the Mocean messaging API into the rest of a workflow. One node, two resources, SMS and Voice, and a single send action on each. Hand it a sender number, a recipient number and a message, and n8n sends it as part of the run. Everything upstream, the data that decides who gets the message and when, comes from the other nodes.

Take a support rota kept in a spreadsheet. A Schedule Trigger reads the rows from Google Sheets, a filter keeps the person on duty tonight, and sms.send pushes the shift reminder to the number stored on that row. Nobody has to remember to send it.

Second pattern: an alert that already lands somewhere quiet. Plenty of teams route incidents to Slack or to Pushover, then lose them overnight. Add a Mocean node at the end of that branch and the same payload also leaves as a text message, with an expression like {{ $json.field }} reading the phone number off the item that opened the branch. An expression is just n8n syntax for pulling a value out of the incoming data instead of typing it by hand.

The third pattern uses the Voice resource. voice.send takes the same From, To and Message, plus an optional Language picked from five locales (cmn-CN, en-GB, en-US, ja-JP, ko-KR). A public n8n template already shows the plain SMS version of the workflow, which is a short read before building your own variant.

When an endpoint of the Mocean API sits outside the 2 operations of the node, the HTTP Request node calls it directly and reuses the same Mocean credential through predefined authentication. That is the standard way out, and it keeps one credential doing all the work.

One thing to know before building: Mocean has no trigger node in n8n, so the workflow is started by something else. If the question is the platform rather than this node, the n8n review covers that ground, and the n8n training goes through the expression syntax used above.

Connect

How do you connect Mocean to n8n?

  1. 01

    Collect the key and the secret

    Mocean issues two values for the credential: an API Key and an API Secret. Both are available in the Mocean Dashboard once the account exists, on the API authentication side. Copy them somewhere temporary, because the next step asks for both at the same time.

  2. 02

    Create the Mocean credential in n8n

    In n8n, open the Credentials menu and create a Mocean credential, the API key method. Paste the API Key and the API Secret into their fields and save. A credential, meaning the stored connection to an outside account, is created once and reused by every workflow, so this step does not come back next time.

  3. 03

    Pick the resource and fill three fields

    Drop the Mocean node into the workflow and select that credential from its dropdown. Choose the resource, SMS or Voice, then fill From, To and Message. All three are required, and n8n stops the node during execution if one of them resolves to an empty value.

Actions

What can the Mocean node do?

The Mocean node exposes 2 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceSend
SMS✓
Voice✓

SMS

1 operation
01

Send an SMS

sms.send

What you see in n8n

Notes & use cases

Selects the SMS resource and pushes a text message out through Mocean. The node works from whatever the incoming item carries, so the send happens mid-workflow and nobody opens a console for it.

Key parameters

  • From: the sender number, as the field placeholder Sender Number indicates.
  • To: the recipient number, placeholder Receipient number, usually an expression such as {{ $json.field }} pointing at the number carried by the previous node.
  • Message: the text of the SMS. Required, so an empty value stops the node.
Use cases
an online order comes in and the confirmation text goes out in the same run, without anyone opening a dashboard to type it.

Voice

1 operation
02

Send an SMS

voice.send

What you see in n8n

Notes & use cases

Same three fields, different channel: with the Voice resource selected, Mocean sends the message as a voice message rather than a text. The choice matters when the person on the other end answers a call faster than they read a screen.

Key parameters

  • From: the sender number (placeholder Sender Number).
  • To: the number to reach, placeholder Receipient number.
  • Message: the message content sent through the Voice resource.
  • Language: the language of the voice message, one of five values (cmn-CN, en-GB, en-US, ja-JP, ko-KR). Not required, so the field can be left alone.
Use cases
a booking that nobody confirmed by the evening gets a voice reminder the next morning, straight from the same workflow.
Need help

Need help automating Mocean with n8n?

A person reads every message.

FAQ

Mocean and n8n: common questions

01Is the Mocean n8n integration free?
On the n8n side, yes. The Mocean node ships with n8n, so there is nothing to install and no extra cost, whether the workflow runs on n8n Cloud or on a self-hosted instance (Community Edition, Sustainable Use licence). A workflow behaves the same in both places, which means you can build it locally and move it later. What a Mocean account itself costs is a separate matter and this page does not cover it. Inside n8n, the Mocean credential is created once from the Credentials menu and reused by every workflow that sends a message.
02Which credentials does the Mocean node need?
An API key credential, and it takes two values: an API Key and an API Secret. Both are accessible in the Mocean Dashboard once the account has been created. Paste them into the Mocean credential in n8n and save. The node itself has no authentication selector, it simply offers the saved credential in a dropdown, so the setup is done in one place rather than repeated on each node. That same credential is what the HTTP Request node reuses through predefined authentication when a call goes outside the two operations.
03What are the limits of the Mocean node in n8n?
The node exposes 2 operations across 2 resources, SMS and Voice, and both take the same three required fields: From, To and Message. Voice adds an optional Language field with five values. For any other endpoint of the Mocean API, the HTTP Request node calls it directly and reuses the same Mocean credential through predefined authentication, so nothing forces you to leave n8n. Keep the required fields in mind while building: a field marked required blocks the node at execution time if the expression behind it resolves to nothing.
04How do you trigger a Mocean workflow with no trigger node?
Mocean has no trigger node in n8n, so the workflow starts somewhere else and the Mocean node sits further down the canvas. Three common starting points: a Schedule Trigger firing at a fixed interval, which suits reminders and daily rotas; an n8n Webhook, meaning a URL n8n exposes so an outside service can call the workflow when something happens on its side; or the trigger of another tool already in the stack. From there the run carries the data forward, and the Mocean node reads the recipient and the message off the item it receives.
05n8n or Make for sending messages with Mocean?
It depends on four things, and neither tool is the wrong answer. Hosting: n8n self-hosts through Docker or npm, and also runs on n8n Cloud, while Make is hosted only. Data control follows from that, since a self-hosted instance keeps the message content on infrastructure you run. Cost model: Make bills per operation, which is worth simulating against the volume of messages you expect. Visual logic: the two editors think differently about branching, so the honest test is to rebuild one real workflow in each and see which one you read faster.
Same platform

Other docs you might need on this stack.

Browse all integrations