Resources · n8n integration

Vonage n8n integrationAutomate Vonage with n8n.

A text message at the end of any workflow. The Vonage n8n integration is one operation, sms.send, on the SMS resource: sender, recipient, body, and 7 optional fields. There is no Vonage trigger, the node that starts a workflow, so the send sits behind whatever already fires.

Try the Vonage integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Vonage n8n integration actually do?

The Vonage n8n integration connects an n8n workflow to the Vonage SMS API through a node that ships with n8n. Its scope fits in one sentence: it sends an SMS. You give it a sender, a recipient number in E.164 format and a message body, and n8n hands the request to Vonage with the API key stored in your credential, the connection you save once and reuse everywhere.

The gesture worth learning is short. Drop the Vonage node right after the step that already knows the number, then point To at that item with an expression, the small piece of code written {{ $json.field }} that reads a value from the item coming in. A number typed by hand gives you one alert. A number read from the item gives you a channel.

First scenario, the on-call alert. A message lands on a queue, the node that reads the queue passes it along, and Vonage turns it into a text on the phone of whoever is awake. The body is built with the same expression style, so the message carries the actual error instead of a generic ping. Keep Slack for the thread the whole team reads, and let the phone buzz only for the person on duty.

Second scenario, the lead that cannot wait. A form fills a row in Google Sheets, a Schedule Trigger reads the new rows at a fixed interval, and each row sends one SMS to the rep who owns it. The sales phone rings before the prospect has closed the tab.

Third scenario, the second road. An email goes out through SendGrid, and the branch that handles a failed send drops down to SMS instead of dying quietly in the execution log.

The node covers the SMS resource and its Send operation. For any other endpoint of the Vonage API, the HTTP Request node takes over: it calls any endpoint and reuses the same credential through predefined authentication. If you want the wider picture before building, the n8n review places the tool, and the n8n training covers expressions and credentials from scratch.

Connect

How do you connect Vonage to n8n?

  1. 01

    Open a Vonage developer account

    The credential n8n expects runs on API key authentication, and the two values behind it only exist inside a Vonage developer account. So that account comes first, before anything else. Until it exists there is nothing to fill in on the n8n side, and no node worth testing.

  2. 02

    Copy the API Key and API Secret

    Sign in to the developer dashboard at dashboard.nexmo.com, then go to user account, Settings, API Settings. Two values sit there: API Key and API Secret. Copy both. That dashboard is where they come from, and Vonage documents the same path under Retrieve your account information.

  3. 03

    Save the credential once in n8n

    In n8n, open the Credentials menu, create a Vonage credential, paste the API Key and the API Secret, save. A credential is created once and reused across every workflow: the Vonage node then offers it in its dropdown, and the key is never retyped inside the node itself.

Actions

What can the Vonage node do?

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

Resources × operations matrix
ResourceSend
SMS✓

SMS

1 operation
01

Send an SMS

sms.send

What you see in n8n

Notes & use cases

One text message goes out for every item that reaches the node, so your item count is your send count.

Key parameters

  • From: the name or number the message is sent from.
  • To: the recipient, in E.164 format, usually read from the step before with {{ $json.field }}.
  • Message: the body of the message being sent.
  • Status Report Req: switch it on to receive a Delivery Receipt, and set Callback to the URL that receipt is sent to, which overrides the one set in the Dashboard.
Use cases
a nightly check texts the owner of each failed row, without anyone typing a number.
Need help

Need help automating Vonage with n8n?

A person reads every message.

FAQ

Questions people ask before building

01Is the Vonage n8n integration free?
Yes on the n8n side. The Vonage node ships with n8n, so there is nothing to install and no extra cost inside n8n, whether the workflow runs on n8n Cloud or on a self-hosted instance in Community Edition under the Sustainable Use licence. The workflow behaves the same in both cases. What Vonage charges for its SMS API belongs to your Vonage account and is not covered here. The only budget on the n8n side is build time: one credential, one node, and the expressions that fill the recipient and the text.
02What credentials does the Vonage node need?
An API key credential, made of two values: API Key and API Secret. A Vonage developer account comes first. Both values are then picked up in the developer dashboard at dashboard.nexmo.com, under user account, Settings, API Settings, and Vonage documents that same path under Retrieve your account information. In n8n the credential is created once from the Credentials menu and reused by every workflow that talks to Vonage, including an HTTP Request node set to predefined authentication. The node offers it in a dropdown afterwards, so the key never gets pasted into a workflow.
03What are the limits of the Vonage node in n8n?
It depends on what you need beyond sending. The node exposes the SMS resource and its Send operation, with three main fields and a collection of 7 additional ones: Account Ref, an account reference for billing that Vonage asks you to enable by emailing support@nexmo.com; Callback; Client Ref, your own reference of up to 40 characters; Message Class, the Data Coding Scheme value from 0 to 3; Protocol ID, which has to stay aligned with udh; Status Report Req; and TTL in minutes, knowing that Vonage attempts delivery for 72 hours by default. For any other endpoint of the Vonage API, the HTTP Request node calls it directly and reuses the same credential.
04Is there a Vonage trigger in n8n?
No. Vonage has no trigger node in n8n, so a workflow that involves it starts somewhere else: a Schedule Trigger running at a fixed interval, an n8n Webhook, meaning a URL that a third-party service calls, or the trigger of another tool. In practice the send always arrives at the end of a chain that something else opened, a new row, a queue message, a failed email. Pick the starting point that already knows the phone number and the text, and the Vonage node has nothing left to guess.
05n8n or Make for Vonage?
It depends on where the data should live. n8n self-hosts with Docker or npm, or runs on n8n Cloud, the hosted offer from n8n, and the workflow is identical either way. Make is hosted only, with no self-hosting option, and bills per operation, which reads differently when a single workflow fans out a batch of messages. So the criteria are hosting, control over your data, cost model and how you like to read a visual flow. Phone numbers and message bodies are personal data, which makes the hosting question a real one rather than a matter of taste.
Same platform

Other docs you might need on this stack.

Browse all integrations