TL;DR: n8n ships no Kixie node, so n8n SMS automation is built from two core nodes instead of one app action, an HTTP Request node to send and a Webhook node to hear the reply. The send is Kixie’s Send SMS API, a POST to https://apig.kixie.com/app/event carrying businessid, email, target, eventname sms, message and apikey, and it needs the Professional Billing Tier or higher; the Team SMS version swaps eventname to bizsms and adds the Team SMS id from Manage, Numbers, Team SMS plus an optional fromNumber, and that is the one whose replies land on a shared number rather than in one rep’s thread. The reply comes back through Kixie’s SMS webhook, which fires on every SMS sent or received and carries direction, message, customernumber, businessnumber, messageid, messageDate and the matched CRM contact, so the direction field is what stops the workflow from firing on your own outgoing texts. Two node settings cause most duplicate messages: Retry On Fail reruns a node until it succeeds, which on a send that timed out after delivery is a second text, and On Error set to Continue moves to the next node using the last valid data, so a failed send logs as a success. The law cares about the reply path too: 47 CFR 64.1200(a)(10) makes stop, quit, end, revoke, opt out, cancel and unsubscribe per se revocations, bars you from naming an exclusive way to opt out, caps honoring at ten business days, and requires a disclosure on every message plus alternative opt-out routes if your texting protocol cannot accept replies, while (a)(12) presumes a confirmation text is covered by prior consent only when it goes out within five minutes. On n8n Cloud, concurrency limits apply to production executions started by a trigger, extra runs queue FIFO, and queued executions cannot be retried. Community edition excludes workflow and credential sharing, so whoever builds this owns it alone.
Why n8n SMS automation starts with a node that does not exist
Open the nodes panel, type Kixie, and nothing comes back. n8n’s integration directory has no Kixie listing and its template library returns zero workflows for the term. Twilio, Vonage, SMS Magic, Salesmsg and ClickSend all have one. Kixie does not.
That is not a dead end. It is the whole design decision, and it is worth understanding before you start dragging nodes onto a canvas.
Kixie is a sales engagement platform for business calling and texting, so what n8n is wiring into is the same account your reps already dial and text from. Kixie’s n8n integration page says the connection runs through Kixie webhooks, the Kixie API and Zapier actions. So you build the automation out of core nodes: an HTTP Request node going out, a Webhook node coming in. An app node is a set of defaults somebody else picked for you. Wire the API yourself and you pick them, which sounds like extra work right up until you notice that the defaults are exactly where this breaks.
Three of them decide whether this works: what the send node does when it fails, whether anything is listening when the customer answers, and who can open the workflow a year from now. Teams running the same build on Make hit the first two as well. The third is specific to n8n, and it is the one nobody checks.
Send the text with the n8n HTTP Request node
Kixie’s Send SMS API is a POST to https://apig.kixie.com/app/event with Content-Type set to application/json. The body carries businessid, email, target, eventname set to sms, message and apikey, and the key also rides on the query string. It requires the Professional Billing Tier or higher.
There is a second version, and the choice between them is not a formatting detail. The Team SMS API sets eventname to bizsms and adds id, the Team SMS ID found under Manage, Numbers, Team SMS. An optional fromNumber picks which number sends when several are attached to that ID; leave it out and Kixie uses the first one. Your API key and Business ID live under Manage, Account Settings, Edit All, Integrations, and the Team SMS API has to be switched on for your account.
So which one? Ask where the answer goes. A personal send puts the reply in one rep’s thread, which is fine until that rep is on vacation and a customer answers a question nobody else can see. Team SMS puts it on a shared number. If the message is from the company rather than from a person, send it as Team SMS and stop pretending a single inbox is a process.
Put the API key in an n8n credential rather than typing it into the node body. Credentials are stored apart from the workflow JSON, which matters the first time somebody exports a workflow to share it.
Hear the reply with the n8n Webhook node
Kixie’s SMS webhook fires every time an SMS is sent or received, and the webhook settings in the Kixie dashboard let you choose incoming, outgoing or all. The payload carries messageid, from, to, customernumber, businessnumber, direction, message, businessid, messageDate and a contact object holding the matched CRM record and a crmlink.
The build is short. Add a Webhook node, copy its URL into Kixie’s webhook settings, then branch on direction.
Branch on it or regret it. Subscribe to all SMS, skip the filter, and the workflow fires on your own outgoing messages too. Every text your team sends starts a run that thinks a customer just replied. That is one of the two ways this design texts people twice, and it shows up as a loop rather than as an error.
The Webhook node tops out at a 16MB payload, which no SMS will ever approach, and it offers four response modes. Immediately returns a response code and the message Workflow got started. When Last Node Finishes returns whatever the final node produced. Using Respond to Webhook hands control to a dedicated node. Streaming is for workflows that return data as they run.
Pick Immediately. Kixie does not need your workflow’s opinion, it needs a fast acknowledgement. Do the lookup, the CRM write and the alert after you have answered.
The n8n settings that turn one text into three
Every n8n node has a Settings tab, and two of its options are quietly dangerous on a node that sends messages to customers.
Retry On Fail reruns a node until it succeeds. Read that again with an SMS send in mind. A send does not fail cleanly. The request times out, the connection drops, the response never arrives, and the message went out anyway. n8n sees a failure. n8n retries. The customer gets a second text, and if the pattern repeats, a third.
On Error has three settings: Stop Workflow halts everything, Continue proceeds to the next node using the last valid data, and Continue using error output passes the error down a separate branch. Continue is the quiet one. The workflow finishes green, the next node writes a CRM activity saying the text was sent, and nothing was sent. Now your rep is looking at a logged message the customer never received.
Two more worth knowing. Execute Once runs the node with the first item only and ignores the rest, so a batch of forty contacts sends one text and reports success. Always Output Data makes a node return an empty item when it had nothing, which keeps a downstream branch running on nothing at all.
So set it like this. Retry On Fail belongs on the nodes that read data, not on the node that sends. Set the send node to Continue using error output and run that branch into something a person sees. A failed send should be visible, not absorbed.
A send-only n8n SMS workflow changes what every message must say
Most teams build the send first and promise to get to replies later. The rule in 47 CFR 64.1200 does not grant that extension, and the detail is worth reading closely because it is unusually specific about architecture.

Paragraph (a)(10) says a called party may revoke consent using any reasonable method. Seven words are reasonable per se when sent in reply to an incoming text: stop, quit, end, revoke, opt out, cancel and unsubscribe. Other words count too, and the standard is whether a reasonable person would understand them as a request to stop. A customer who answers “please take me off this” has revoked, and no keyword match is going to catch that.
Then comes the clause that reaches into your canvas. If the sender uses a texting protocol that does not allow reply texts, it must provide a clear and conspicuous disclosure on each text that two-way texting is not available due to technical limitations, and clearly and conspicuously provide on each text reasonable alternative ways to revoke consent.
Read that against a workflow that is only an HTTP Request node. Skipping the Webhook node does not just lose replies. It changes what every single message you send has to contain.
Two more constraints land on the same build. Revocation requests have to be honored within a reasonable time not to exceed ten business days. And you may not designate an exclusive means of revocation, so a workflow whose only opt-out path is a STOP keyword match is not a plan, it is one of several routes you have to support. The current consent and opt-out rules cover the rest of that ground.
Paragraph (a)(12) then turns a timing requirement into a node choice. A single confirmation text after a revocation is allowed, as long as it only confirms, carries no marketing and is the only additional message sent. Deliver it within five minutes and it is presumed to fall within the customer’s prior express consent. Take longer and the sender has to show the delay was reasonable.
Five minutes is a design requirement, not a nicety. A Schedule Trigger polling every fifteen minutes cannot meet it on its worst run. A Webhook trigger can, because it starts the moment the reply lands. The compliance rule and the node choice are the same decision.
Where n8n SMS automation queues and what you cannot retry
n8n Cloud caps how many production executions run at once, and the cap goes by plan. Anything over the cap queues and runs FIFO as capacity frees up. That limit applies only to production executions, meaning the ones a webhook or trigger node started. Manual runs, sub-workflow runs and error executions sit outside it.
Now the sentence that should change your send design. Queued executions cannot be retried. Cancelling or deleting one also removes it from the queue. On restart, n8n resumes queued executions up to the limit and re-enqueues the rest.
Think about the shape of an SMS campaign. You send four hundred texts in a burst, replies come back in a wave over the next ten minutes, and each reply starts a production execution. The runs that queue are the inbound replies during your busiest window. The ones you would most want to retry are precisely the ones you cannot.
The fix is upstream, not downstream. Throttle the send so the replies do not arrive as a single wave. Batch the outbound list with a Loop node and a Wait node between batches, and the reply traffic spreads across a window your plan’s concurrency can absorb. This is the same reasoning that applies to call volume, where pacing an n8n and PowerDialer integration beats a spike nobody can staff.
Why the n8n SMS workflow fired once and never again
This is the most common support question in the category, and it is always the same cause.

The Webhook node has two URLs, test and production. n8n registers a test webhook when you select Listen for Test Event, or when you execute a workflow that is not active. It registers the production webhook when you publish the workflow. With the production URL, n8n does not show the incoming data on the canvas; you read it in the Executions tab instead.
So the failure writes itself. You build with the test URL because it shows you the payload, you paste that URL into Kixie’s webhook settings, you watch a real reply arrive, and you ship. The test registration disappears the moment the editor stops listening. Kixie keeps posting to a URL nobody is answering, and every reply after the demo goes nowhere.
Set an error workflow while you are in there. You assign one per workflow in Workflow Settings and it must start with the Error Trigger node. One error workflow can serve many workflows, and the Stop And Error node lets you fail on purpose, which is the right move when a contact arrives with no consent field.
Know its blind spot before you trust it. The error data normally includes execution.id and execution.url, but neither is present when the error is in the trigger node of the main workflow, because the workflow never executed. The inbound reply that failed at the door is the one your alert can say the least about.
Who can open the n8n SMS workflow after you build it
Here is the question nobody asks during the build, and it is the one that costs the most later.
n8n’s Community edition is free and carries almost the complete feature set. What it leaves out matters here: sharing of workflows and credentials is not included, so only the instance owner and the user who created them can access them. Version control using Git is not included. Neither are projects, log streaming, environments, external secrets or SSO.
Translate that into staffing. One person builds the SMS workflow. That person holds the credential that sends from your company number. That person is the only one who can open it. When they leave, the workflow keeps texting your customers and nobody can read it, change it, or turn it off from inside the editor.
That is the same failure as a deal that lives in a rep’s notebook. The work is getting done and the company does not own it.
Registering the Community edition is free and unlocks folders, debug in editor and custom execution data. It does not add sharing. So this is a real decision with a price on it: self-host free and accept single ownership, or move to a plan where a second person can open the thing that texts your customers. Make it deliberately, and write down who the second person is.
Lock down the inbound n8n SMS webhook
The Webhook node supports Basic auth, Header auth, JWT auth, n8n User Auth via OAuth2, and None.
None is a selectable option, and it is the shortest path to a working demo. It is also a public URL that anybody who learns it can POST to. Think about what that endpoint receives: customer phone numbers, message bodies, and the matched CRM contact with name, email and a link straight into your CRM record.
Kixie’s SMS webhook payload carries a webhookHeaders field, so Header auth is the option that lines up with it. Add the IP allowlist option to limit which addresses can invoke the trigger. Turn on Ignore Bots so link previewers and crawlers do not start executions. Leave the randomly generated path alone, because it exists to avoid collisions and a guessable path is one less thing in your favor.
None of this is exotic. It is four toggles, and it is the difference between an endpoint scoped to your messaging provider and one scoped to the internet.
Consent and 10DLC rules your n8n SMS workflow will not handle
n8n moves data between systems. It does not register your brand with the carriers, it does not hold your consent record, and it has no opinion about whether this particular person agreed to be texted.
On the carrier side, Twilio’s A2P 10DLC documentation states that registering results in lower message filtering and higher messaging throughput, and that customers who send from a 10DLC number without registering will receive additional carrier fees for unregistered traffic. The 10DLC compliance checklist for outbound texting walks the registration itself.
On the consent side, the field that records opt-in has to live somewhere the workflow can read before the send, not in a spreadsheet somebody updates on Fridays. Put an If node ahead of the HTTP Request node that checks it. Route a missing value into a Stop And Error node so the run fails loudly instead of texting somebody who never agreed.
The opt-out path needs the same treatment in reverse. When a reply matches a revocation, write it back to the consent field before you do anything else in that branch. Ten business days is the outer limit, not the target, and the record is what proves you honored it.
Build the reply path first, pick the send version second, set the node error behavior third, and decide who else can open it before anybody calls it done. The send was the easy part.
n8n SMS automation FAQs
Can n8n send SMS without a dedicated Kixie node
Yes. n8n’s integration directory has no Kixie node, so the send runs through the HTTP Request node calling Kixie’s Send SMS API, a POST to https://apig.kixie.com/app/event with businessid, email, target, eventname sms, message and apikey. The API requires the Professional Billing Tier or higher. Nothing about the core-node path is a workaround; it is what Kixie’s own n8n integration page describes.
How do inbound SMS replies reach an n8n workflow
Through a Webhook node whose URL you paste into Kixie’s webhook settings. Kixie’s SMS webhook fires on every SMS sent or received, and the dashboard lets you scope it to incoming, outgoing or all. Branch on the direction field so the workflow does not also fire on your own outgoing messages, and use the production webhook URL rather than the test URL, which only registers while the editor is listening.
Why does an n8n SMS automation send duplicate texts
Usually Retry On Fail on the send node. It reruns the node until it succeeds, and an SMS send that timed out after the message already went out looks like a failure, so the retry delivers a second copy. The other common cause is a webhook subscribed to all SMS instead of incoming only, which makes your own outgoing text start a run that behaves as though a customer replied.
Does n8n SMS automation need 10DLC registration
Yes for US traffic sent from a 10DLC number, though the requirement attaches to the number and the traffic rather than to n8n. Twilio’s A2P 10DLC documentation states that registering lowers message filtering and raises throughput, and that unregistered traffic from a 10DLC number picks up additional carrier fees. n8n does not register anything on your behalf, so handle the brand and campaign registration with your messaging provider before the workflow goes live.
Sources
- n8n, integrations directory, which lists the available app nodes and returns no Kixie listing while Twilio, Vonage, SMS Magic, Salesmsg and ClickSend SMS each resolve to a node page. https://n8n.io/integrations/. Reviewed November 14, 2026.
- n8n documentation, Webhook node, giving the test and production webhook URLs and when each is registered, the Basic, Header, JWT, n8n User Auth and None authentication options, the 16MB maximum payload, the Immediately, When Last Node Finishes, Respond to Webhook and Streaming response modes, and the Allowed Origins, Binary Property, Ignore Bots and IP allowlist options. https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/. Reviewed November 14, 2026.
- n8n documentation, nodes, describing the node Settings tab and defining Always Output Data, Execute Once, Retry On Fail and the Stop Workflow, Continue and Continue using error output options for On Error. https://docs.n8n.io/workflows/components/nodes/. Reviewed November 14, 2026.
- n8n documentation, handle errors gracefully, stating that an error workflow is set per workflow in Workflow Settings and must begin with the Error Trigger, listing the error payload fields, noting that execution.id and execution.url are absent when the error occurs in the trigger node because the workflow does not execute, and describing the Stop And Error node. https://docs.n8n.io/flow-logic/error-handling/. Reviewed November 14, 2026.
- n8n documentation, understand concurrency, stating that n8n Cloud limits concurrent production executions by plan, that excess executions queue and are processed in FIFO order, that the limit applies only to executions started from a webhook or trigger node, that queued executions cannot be retried, and that on startup n8n resumes queued executions up to the limit and re-enqueues the rest. https://docs.n8n.io/manage-cloud/concurrency/. Reviewed November 14, 2026.
- n8n documentation, compare editions, stating that the Community edition excludes sharing of workflows and credentials so that only the instance owner and the user who creates them can access them, and also excludes version control using Git, projects, log streaming, environments, external secrets and SSO, while the free Registered Community edition adds folders, debug in editor and custom execution data. https://docs.n8n.io/hosting/community-edition-features/. Reviewed November 14, 2026.
- Electronic Code of Federal Regulations, 47 CFR 64.1200, paragraphs (a)(10) through (a)(12), giving the seven per se revocation words, the reasonable-person standard for other wording, the bar on designating an exclusive means of revocation, the ten business day deadline, the per-message disclosure and alternative opt-out routes required when a texting protocol cannot accept replies, and the single confirmation text allowance with its five minute presumption. https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200. Reviewed November 14, 2026.
- Twilio, A2P 10DLC documentation, stating that registering for A2P 10DLC results in lower message filtering and higher messaging throughput, and that customers sending from a Twilio 10DLC number without registering receive additional carrier fees for unregistered traffic. https://www.twilio.com/docs/messaging/compliance/a2p-10dlc. Reviewed November 14, 2026.
- Kixie, Send SMS API documentation, giving the POST endpoint https://apig.kixie.com/app/event, the businessid, email, target, eventname, message and apikey parameters, and the Professional Billing Tier requirement. https://www.kixie.com/developer/sms-api/. Reviewed November 14, 2026.
- Kixie, Team SMS API documentation, giving the bizsms eventname, the required Team SMS id from Manage, Numbers, Team SMS, the optional fromNumber and its default to the first attached number, and the location of the API key and Business ID under Manage, Account Settings, Edit All, Integrations. https://www.kixie.com/developer/team-sms-api/. Reviewed November 14, 2026.
- Kixie, SMS Webhook documentation, stating that the webhook fires every time an SMS is sent or received, that the dashboard settings scope it to incoming, outgoing or all SMS, and listing the payload fields including messageid, from, to, customernumber, businessnumber, direction, message, messageDate, webhookHeaders and the matched contact. https://www.kixie.com/developer/text-message-webhooks/. Reviewed November 14, 2026.
Sources verified and content reviewed by the Kixie Research Team on November 14, 2026.
Ready to close more deals with Kixie?
See how Kixie's AI-powered tools can transform your sales and support operations.
Start Free Trial