seven n8n integrationAutomate seven with n8n.
One node, two ways to reach a phone. The seven n8n integration covers 2 operations across 2 resources: send an SMS, or have a written text read out loud in a voice call. No trigger node ships with seven, so the workflow starts elsewhere, from a schedule or another app, and seven closes it.
Verified Trustpilot reviews · AI, automation & growth agency
What does the seven n8n integration actually do?
The seven n8n integration plugs the seven node, shipped with n8n, into any workflow that needs to reach someone on their phone. Two operations, no more: sms.send pushes a text message to one or several numbers, voice.send turns a written message into a voice call. Both run on a single API key credential, and both ask for the same two required fields, To and Message.
First scenario, appointment reminders. A Google Sheets tab keeps one row per booking, a Schedule Trigger reads it every morning, and sms.send texts each customer the slot they picked. The number never gets typed by hand: it comes from the row through an expression like {{ $json.phone }}, the n8n way of pointing at a field of the incoming item.
Second scenario, the alert that has to land. An incident posted in Slack or on Telegram is easy to miss at two in the morning. Branch the same workflow into voice.send and seven dials the phone of whoever is on duty, then reads the message aloud. A notification waits. A ringing phone insists.
Third scenario, the short version of a long email. Gmail sends the full order confirmation, seven sends the tracking number as one text, both off the same item in the same execution. Customers who never open their inbox still get the single line they were waiting for.
Two ceilings shape what you can write. Message stops at 1520 characters, so a chatty template gets trimmed upstream. The From caller ID on an SMS takes at most 16 numeric characters or 11 alphanumeric ones, which rules out long brand names. On a voice call, From only accepts verified sender IDs, one of your virtual inbound numbers, or a shared virtual number. And when the operation you need is missing from the dedicated node, the HTTP Request node calls any endpoint of the seven API while reusing the same credential, the login details saved once inside n8n.
Worth knowing before you commit: seven has no trigger node in n8n, so the tool sits at the end of a branch, never at the start. If the platform itself is what you are still weighing, the n8n review walks through hosting and cost. Teams that build this kind of flow weekly tend to document the node and the key once, then reuse both everywhere.
How do you connect seven to n8n?
- 01
Create your seven API key
Sign in to the seven developer account the credential will be tied to, then open Account, then Developer, then API Keys. Generate a key there and copy it before you leave the page. API key is the only authentication method the seven node supports, so this single string is what stands between a workflow and messages actually going out.
- 02
Save it as an n8n credential
In n8n, open the Credentials menu and create a seven credential, then paste the key into the API Key field. A credential is a set of secrets stored once inside n8n and reused everywhere: every future seven node offers it in a dropdown list, so the key lives in one place instead of being copied into each workflow by hand.
- 03
Pick the resource and the operation
Add the seven node to the canvas and select the credential you just saved. Choose the Resource, SMS or Voice Call, then the operation underneath it. That pair decides what the node does, and the fields below change with it. Fill in To and Message, both required, because an empty required field stops the execution before anything leaves.
What can the seven node do?
The seven 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.
| Resource | Send |
|---|---|
| SMS | ✓ |
| Voice Call | ✓ |
SMS
1 operationSend an SMS
sms.sendWhat you see in n8n
Notes & use cases
Pushes a text message to one or several numbers and hands the dispatch result back to the rest of the workflow.
Key parameters
- To: the recipient numbers separated by a comma, plain numbers or a contact or group stored in seven (
+49876543210, MyGroup), often{{ $json.phone }}. - Message: the text that goes out, up to 1520 characters.
- From: the caller ID shown on the receiver's display, 16 numeric or 11 alphanumeric characters at most.
- Delay: an Options field that picks a date for a time delayed dispatch instead of sending straight away.
Voice Call
1 operationConvert text to voice
voice.sendWhat you see in n8n
Notes & use cases
Turns written text into a spoken call: seven dials the number and reads the message out loud, which suits anything that cannot wait for someone to open an app.
Key parameters
- To: the number called, comma separated for several recipients, and contacts or groups stored in seven work here too.
- Message: the script read aloud, with the same 1520 character ceiling as the SMS operation.
- From: an Options field for the caller ID, limited to verified sender IDs, one of your virtual inbound numbers, or a shared virtual number.
Need help automating seven with n8n?
A person reads every message.
