MessageBird n8n integrationAutomate MessageBird with n8n.
Two jobs, one node: push a text message out, and read the account balance. The MessageBird n8n integration covers 2 operations across 2 resources, with 3 required fields on the send and 11 optional ones behind Additional Fields. There is no MessageBird trigger, so another node starts the run.
Verified Trustpilot reviews · AI, automation & growth agency
What does the MessageBird n8n integration actually cover?
MessageBird sends text messages, and the account behind it is a Bird account. The n8n node is a short, direct bridge to it: 2 operations spread over 2 resources, SMS and Balance. The node ships with n8n, on Cloud and on a self-hosted instance alike, so there is nothing to install and nothing extra to pay on the n8n side. One API key, saved once as a credential, is all the authentication it asks for.
Start with the obvious one. A parcel leaves the warehouse, the carrier writes the tracking reference into a row, and the buyer gets a text within the minute. The row lives in Google Sheets, the phone number comes out of it as an expression, and sms.send does the rest. An expression is just a reference to a field of the incoming item, written {{ $json.field }}.
The second pattern is internal. A nightly sync fails at 4am, and an email nobody reads until morning is not much of an alert. Branch the failure path into MessageBird, text whoever is on call, and post the same message into Slack for the written record. Same workflow, two channels, one condition.
Third, the quiet one: Balance. A Schedule Trigger, which runs a workflow at a fixed interval, reads the balance once a day and writes it somewhere visible. Nothing clever, but it turns an account number into something the team actually looks at.
A few behaviors are worth knowing before you build. Switching Datacoding to Unicode caps the message at 70 characters instead of 160. Group IDs takes a comma separated list, and when it is filled the recipients field can be left out. Report Url sets a status report URL for that one message, and a Reference has to be set for a status report webhook to be sent, a webhook being a URL that a service calls back. Type Details only comes into play when a binary message is sent.
The node's catalogue holds those 2 operations and no more. For any other endpoint of the Bird API, the HTTP Request node calls it directly and reuses the same MessageBird credential through its predefined authentication, so you keep one key for everything. If the whole n8n side is new to you, the n8n training walks through credentials, expressions and error branches on real workflows.
How do you connect MessageBird to n8n?
- 01
Generate the API key
You need a Bird account first, since that is where the MessageBird credential is issued. Open the Access keys page in the Bird app and create a key there. API key is the authentication method the n8n credential supports, so this key is the one thing you carry over into n8n. Keep it at hand for the next step.
- 02
Save the credential in n8n
In n8n, go to the Credentials menu and create a MessageBird credential. There is a single field to fill, API Key, and you paste the key from the Bird app into it. A credential is stored once and reused everywhere: every MessageBird node in every workflow will offer it in a dropdown, so you never paste the key into a node again.
- 03
Wire the node and pick an operation
Drop a MessageBird node on the canvas, select the credential in its list, then choose a resource. SMS gives you Send, Balance gives you Get. Run the node on its own before connecting anything upstream: a single execution on Balance tells you whether the key works, without sending a message to a real phone number.
What can the MessageBird node do?
The MessageBird 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.
SMS
1 operationSend an SMS
sms.sendWhat you see in n8n
Notes & use cases
This operation hands MessageBird the text and the recipient list, and MessageBird sends it. Three fields are required, everything else sits in the Additional Fields collection.
Key parameters
- From: the number the message is sent from, in the shape of
14155238886. - To: all recipients separated by commas, with or without the leading plus. Map it from the incoming item with
{{ $json.field }}. - Message: the text to send. Left empty it blocks the run, like any required field.
- Datacoding: Auto, Plain or Unicode. Unicode caps the message at 70 characters instead of 160.
Balance
1 operationGet the current balance
balance.getWhat you see in n8n
Notes & use cases
Balance carries a single operation and it asks for no configuration at all: pick the resource, pick Get, run the node. n8n returns the current account balance as one item, ready to compare, log or forward.
Need help automating MessageBird with n8n?
A person reads every message.
