Wakala wa AI wa WhatsApp katika n8n, na jibu linaandikwa na workflow yako
Hatua ya otomatiki hutuma POST ya ujumbe wa mteja, uliotiwa sahihi na hadi jumbe 10 za hivi karibuni za mazungumzo, kwa node ya Webhook ya n8n. Node ya AI Agent huandika jibu, node ya Respond to Webhook hurudisha {"reply": "..."} ndani ya sekunde 20, na maandishi hayo hutumwa kutoka nambari yako ya WhatsApp Business, ambayo inaendelea kufanya kazi kwenye programu. Wakala wanaochelewa zaidi hupokea webhook ya Meta moja kwa moja na kujibu kupitia Graph API.
easyCoexistence huunganisha nambari yako ya WhatsApp Business unayotumia tayari kwenye programu kwenye Cloud API ya Meta kupitia Coexistence, na huendesha otomatiki juu yake.
Muda ambao hatua ya Call my webhook husubiri jibu la workflow yako kabla hatua haijashindwa.
Jumbe za hivi karibuni za mazungumzo zinazotumwa kwenye history, za zamani kwanza, zikiishia na ujumbe uliozindua mchakato.
Idadi ya herufi za jibu linalotumwa kama ujumbe mmoja wa maandishi wa WhatsApp; kinachozidi hukatwa.
Muda mfupi zaidi kati ya barua pepe mbili za hitilafu kwa otomatiki ile ile hatua ya webhook inaposhindwa.
Kinachoruhusiwa na n8n Cloud katika node ya Code: crypto na moment; n8n ya kujiendesha yenyewe huwezesha crypto kwa NODE_FUNCTION_ALLOW_BUILTIN.
Dirisha la huduma kwa wateja baada ya ujumbe wa mwisho wa mteja; baada ya hapo Meta inakubali ujumbe wa kiolezo pekee.
Ujumbe wa WhatsApp hufikaje kwa wakala wa AI wa n8n?
Kupitia otomatiki kwenye nambari. Nambari lazima ipokee jumbe zake kupitia easyCoexistence (hali ya "Through easyCoexistence"), ili Meta iwasilishe jumbe hizo hapa. Otomatiki yenye kichocheo A message arrives na hatua Call my webhook hutuma POST ya ujumbe kwenye URL ya Production ya n8n yako. Workflow hujibu katika jibu lile lile la HTTP, na maandishi yanayorudishwa hufika kwa mteja kama ujumbe wa WhatsApp kutoka nambari yako.
Kabla n8n haijaitwa, mchakato tayari umepita ulinzi. Usambazaji ambao Meta hurudia haianzishi mchakato wa pili kamwe, jibu ulilolandika kwenye programu husitisha otomatiki kwenye mazungumzo hayo (saa 4 kwa chaguo-msingi), na jibu hutumwa tu ndani ya saa 24 za ujumbe wa mwisho wa mteja. Workflow yako huamua tu la kusema.
easyCoexistence hutuma nini kwenye node ya Webhook ya n8n?
POST ya JSON yenye User-Agent easyCoexistence-automations/1, X-EC-Event iliyowekwa automation.step, na kichwa X-EC-Signature. message ina maandishi ya mteja, au kishikilia nafasi kama [image] pamoja na maelezo kwa media; ujumbe wa sauti hufika kama [voice message] ikifuatiwa na maneno yake ufunguo wa OpenAI au OpenRouter ukihifadhiwa. history ina hadi jumbe 10 za hivi karibuni za mazungumzo, za zamani kwanza, kila moja ikiwa na direction: in kwa mteja, out kwa jibu la otomatiki, na echo kwa mtu anayeandika kutoka simuni. Inahusu jumbe zilizohifadhiwa kwa kipindi cha uhifadhi cha akaunti (siku 30, 90 au 365, siku 90 kwa chaguo-msingi), na zile tu zilizofika wakati jumbe za nambari zilikuwa zikipita kupitia easyCoexistence.
Jaribio kutoka kwenye paneli ya Try it ya kihariri hutuma POST ile ile yenye dry_run iliyowekwa true, history tupu, mteja wa majaribio 15550000000 aitwaye Test customer, na message id inayoanza na test_. Hakuna anayetumiwa chochote, lakini workflow yako inaendeshwa kweli, kwa hiyo ruka vitendo kama kuunda oda dry_run inapokuwa true.
{
"event": "automation.step",
"dry_run": false,
"automation": { "id": "b7e0c3a2-5d1f-4c8e-9a6b-2f4d8e1c7a90", "name": "Send to my system" },
"run_id": "0d9f6a41-8c2e-4b7a-a315-6e9c2b8d4f17",
"channel": {
"type": "whatsapp",
"connection_id": "3f2a9c1e-7b4d-4e8a-9c2f-1a2b3c4d5e6f",
"phone": "+1 631-555-0142",
"phone_number_id": "106540352242922"
},
"connection": { "id": "3f2a9c1e-7b4d-4e8a-9c2f-1a2b3c4d5e6f", "phone": "+1 631-555-0142", "phone_number_id": "106540352242922" },
"contact": { "id": "5511987654321", "wa_id": "5511987654321", "name": "Ana Souza" },
"message": {
"id": "wamid.HBgNNTUxMTk4NzY1NDMyMRUCABIYFjNFQjBDNzE4RjQ2QjI5RDkxQTNFAA==",
"type": "text",
"text": "Do you have gluten-free bread today?",
"at": "2026-11-11T14:02:11.000Z"
},
"history": [
{ "direction": "in", "text": "Hi! Are you open today?", "at": "2026-11-11T13:58:40.000Z" },
{ "direction": "out", "text": "Hi Ana! Yes, until 8 pm.", "at": "2026-11-11T13:58:45.000Z" },
{ "direction": "in", "text": "Do you have gluten-free bread today?", "at": "2026-11-11T14:02:11.000Z" }
]
}Unathibitishaje sahihi katika n8n?
Ongeza node ya Code mara baada ya node ya Webhook. X-EC-Signature inasomeka t=<sekunde za unix>,v1=<hex>, ambapo v1 ni HMAC-SHA256 ya t, nukta na mwili wa ombi, ikitumia Signing secret ya otomatiki kama ufunguo. Ili kuinakili, fungua otomatiki iliyohifadhiwa na uchague hatua yake ya Call my webhook. Kila otomatiki ina siri yake, na zana za MCP hazirudishi siri hiyo kamwe, kwa hiyo otomatiki uliyoundiwa na AI bado inahitaji nakala hii moja kutoka kwenye dashboard. Kitufe cha New secret huibadilisha na ile ya zamani huacha kufanya kazi mara moja, na ni mmiliki wa akaunti pekee anayeweza kuiona, si mwanachama wa timu aliyealikwa.
Kataa t iliyo zaidi ya dakika 5 kutoka saa yako, linganisha kwa muda usiobadilika, na urushe hitilafu inaposhindwa: workflow hushindwa kabla ya Respond to Webhook, n8n hujibu 500, na hakuna kinachotumwa. n8n Cloud inaruhusu moduli ya crypto kwenye node za Code; n8n ya kujiendesha yenyewe inahitaji NODE_FUNCTION_ALLOW_BUILTIN=crypto. Kitendo cha Hmac cha node ya Crypto pamoja na node ya IF pia kinafanya kazi, ingawa ulinganisho wa IF si wa muda usiobadilika.
// n8n Code node, mode "Run Once for Each Item", placed right after the Webhook node.
// n8n Cloud allows require('crypto'); self-hosted needs NODE_FUNCTION_ALLOW_BUILTIN=crypto.
const crypto = require('crypto');
const SECRET = 'whsec_...'; // the automation's Signing secret, from its editor page
const m = /^t=(\d+),v1=([0-9a-f]{64})$/.exec($json.headers['x-ec-signature'] || '');
if (!m) throw new Error('Missing X-EC-Signature');
if (Math.abs(Date.now() / 1000 - Number(m[1])) > 300) throw new Error('Stale signature');
// The body was signed as compact JSON, which JSON.stringify rebuilds from the parsed body.
const mac = crypto.createHmac('sha256', SECRET).update(`${m[1]}.${JSON.stringify($json.body)}`).digest();
if (!crypto.timingSafeEqual(mac, Buffer.from(m[2], 'hex'))) throw new Error('Bad signature');
return { json: $json.body }; // event, dry_run, contact, message, history...Unaweka vipi node ya AI Agent na jibu?
Mpe node ya AI Agent maandishi ya mteja kama ujumbe wake wa mtumiaji, na kila kitu kingine kwenye ujumbe wake wa mfumo: biashara ni nani, ukweli inaoruhusiwa kunukuu, sauti ya mazungumzo, na mazungumzo ya hivi karibuni kutoka history ili swali la ufuatiliaji lieleweke. Ambatisha modeli ya gumzo unayotaka, pamoja na zana kama HTTP Request tool inayotafuta oda.
Malizia kwa node ya Respond to Webhook inayojibu kwa JSON na kuweka maandishi ya wakala kwenye sehemu iitwayo reply. easyCoexistence hukata nafasi za ziada, hupuuza jibu tupu au lisilo la maandishi, na hutuma iliyobaki kama ujumbe mmoja wa WhatsApp wa herufi hadi 4,096. Kwa hiyo mwombe modeli sentensi tupu badala ya markdown.
AI Agent node
Prompt: Define below
Prompt (User Message): {{ $json.message.text }}
Options > System Message:
You answer WhatsApp messages for Bloom Café, 12 Baker St, open Tue to Sun 8:00 to 20:00.
Reply in 1 to 3 short sentences, in the customer's language, as plain text.
Never invent prices or stock. If unsure, say a person will reply here soon.
Recent chat, oldest first:
{{ $json.history.map(h => (h.direction === 'in' ? 'Customer: ' : 'Business: ') + h.text).join('\n') }}
Chat Model: your OpenAI, Anthropic or OpenRouter model
Tools (optional): an HTTP Request tool that looks up orders
Respond to Webhook node
Respond With: JSON
Response Body: { "reply": {{ $json.output.toJsonString() }} }Nini hutokea workflow ikiwa polepole, inashindwa au hairudishi chochote?
Kila matokeo huandikwa kwenye kichupo cha Runs cha otomatiki, pamoja na matokeo au hitilafu ya hatua, ili uone ni ipi kati ya hizi iliyotokea:
- Hakuna jibu ndani ya sekunde 20: hatua inashindwa na Webhook did not answer, hakuna kinachotumwa, na mchakato unaonyesha Failed.
- Hali nje ya 2xx, ikiwemo uelekezaji upya: hatua inashindwa na Webhook answered HTTP na msimbo wake.
- 2xx bila kamba ya jibu: mchakato ni Done, hatua inaonyesha HTTP 200, hakuna jibu, na mteja hapokei chochote kiotomatiki.
- Mchakato ulioshindwa hukutumia barua pepe ili ujibu mteja huyo mwenyewe, mara moja kwa otomatiki kila saa 6 kwa kiwango cha juu.
- Mazungumzo uliyojibu kutoka simuni ndani ya kipindi cha kusitisha (saa 4 kwa chaguo-msingi, zimewekwa chini ya Advanced) yanaruka kama
human_activekabla n8n haijaitwa. - Ujumbe kadhaa wa haraka huanzisha michakato kadhaa. Wait ya dakika 1 kabla ya Call my webhook hujibu mara moja, kwa sababu ujumbe mpya unaochagua otomatiki ile ile hubatilisha mchakato unaosubiri.
Ni lini n8n ipokee webhook ya Meta moja kwa moja?
Wakala anapohitaji zaidi ya sekunde 20, workflow lazima ione kila tukio (hali, majibu yako ya simuni, vitambulisho vya media), inapotuma kitu ambacho hakuna hatua inayokifunika, kama Flow au ujumbe wa katalogi, au biashara inapotaka uingizaji wa historia wa miezi 6. Uingizaji huo huenda tu kwenye marudio ya moja kwa moja yaliyohifadhiwa ndani ya saa 24 tangu kuunganisha. Hali ya moja kwa moja huzima otomatiki kwa nambari: Meta hutuma payload yake moja kwa moja kwa n8n, na easyCoexistence haioni jumbe kamwe.
Kwenye n8n, tumia node ya kawaida ya Webhook, si node ya WhatsApp Trigger, ambayo inatarajia programu yako ya Meta na siri yake. Washa Allow Multiple HTTP Methods ili njia moja ndefu isiyo ya kawaida ipokee GET ya uthibitishaji wa Meta na POST. Jibu GET kwa hub.challenge ghafi kama maandishi, kisha uhifadhi URL hiyo ya Production pamoja na verify token kupitia set_webhook_destination. Majibu hutumwa kisha kutoka node ya HTTP Request hadi endpoint ya kutuma, na dedupe, kusitisha simuni na ukaguzi wa saa 24 vinakuwa vyako.
| Call my webhook (Automations on) | Direct webhook (automations off) | |
|---|---|---|
| Who calls n8n | easyCoexistence, when the automation matches | Meta, for every event on the number |
| Time to answer | 20 seconds, reply in the response | No limit: send later through the Graph API |
| Authentication | X-EC-Signature with the automation's secret | A long random secret in the URL path |
| Guards | Dedupe, phone pause and 24-hour check built in | Yours to write |
| What n8n can send | Text in the reply; the other steps of the automation can send buttons, files and templates | Any Cloud API message type, templates included |
| History import | Not available | If saved within 24 hours of connecting |
| Kept by easyCoexistence | Message text for your retention period (90 days by default), run logs 30 days | Nothing |
Jinsi ya kuisanidi
- Turn on automations for the numberOn the number's page, the Automations and incoming messages card shows Automations on or Direct to your server. Click Turn on automations if needed; numbers connected without a webhook URL start with automations on.
- Build and publish the workflowWebhook node (POST, Respond: Using 'Respond to Webhook' Node), Code node, AI Agent node, Respond to Webhook node. Publish or activate it and copy the Production URL.
- Create the automation, switched OffIn Automations, click New automation and pick Send to my system under Start from an example. Paste the Production URL into Webhook URL, set the switch to Off so it does not answer customers yet, and click Save.
- Copy the Signing secret into n8nSelect the Call my webhook step of the saved automation, copy Signing secret and paste it into the Code node.
- Test, then switch it OnClick Test, type a sample message in Try it and press Run test: n8n runs with dry_run true and the result shows the reply. When it reads right, switch the automation On and save.
Makosa ya kawaida
- Kuacha chaguo la Respond la node ya Webhook kwenye Immediately. n8n hujibu Workflow got started mara moja, mchakato huandika HTTP 200, hakuna jibu, na mteja hapokei chochote. Chagua Using 'Respond to Webhook' Node.
- Kubandika URL ya Test, ile yenye /webhook-test/. Inasikiliza tu wakati kihariri kinasubiri tukio la majaribio; otomatiki zinahitaji URL ya Production ya workflow iliyochapishwa.
- Kuthibitisha kwa siri ya usambazaji ya nambari. Call my webhook imetiwa sahihi kwa Signing secret ya otomatiki yenyewe; siri ya usambazaji hutia sahihi matukio yaliyosambazwa pekee, kwa hiyo hatua halisi hushindwa ukaguzi.
- Kurudisha maandishi kwa umbo jingine. Ni mwili wa JSON wenye kamba ya kiwango cha juu iitwayo reply pekee ndio hutumwa; {"output": "..."} au mwili wa text/plain huandikwa kama no reply.
Hatua yake ya Call my webhook humpa n8n ujumbe wa mteja na kurudisha jibu, pamoja na dedupe, kusitisha unapojibu kutoka simuni na ukaguzi wa saa 24 uliojengwa ndani, bila ada ya ziada kwa kila mchakato. US$ 9 hadi US$ 0.75 kwa kila nambari kwa mwezi, kadri unavyoongeza nambari, na siku 3 za kwanza bila malipo.
Maswali yanayoulizwa mara kwa mara
Je, ChatGPT au Claude wanaweza kuniundia otomatiki hii?
Ndiyo. Baada ya kuongeza kiunganishi cha easyCoexistence, omba otomatiki kwenye nambari yako inayotuma jumbe zinazoingia kwenye URL yako ya n8n. AI itaita create_automation pamoja na hatua ya call_webhook, kisha test_automation. Muombe aiunde ikiwa imezimwa hadi jaribio lipite. Signing secret hairudishwi kupitia MCP, kwa hiyo iinakili kutoka ukurasa wa otomatiki.
Je, workflow inaweza kutuma picha, vitufe au violezo?
Si kupitia sehemu ya reply, ambayo hubeba maandishi pekee. Acha otomatiki ifanye hivyo badala yake: hatua kama Send a picture or file, Ask a question with buttons na Send a template zinaweza kuwa kabla au baada ya Call my webhook. Kwa aina nyingine za ujumbe, zituma kutoka node ya HTTP Request kwenda Cloud API, ukitumia endpoint ya kutuma na token ambazo get_api_credentials hurudisha, na usirudishe reply ili mteja asijibiwe mara mbili.
Je, workflow moja inaweza kujibu nambari kadhaa?
Ndiyo. Elekeza otomatiki moja kwa kila nambari kwenye URL ile ile ya Production, na utofautishe kwa channel.phone_number_id au automation.id. Kila otomatiki ina Signing secret yake, kwa hiyo chagua siri kwa automation.id kabla ya kukagua sahihi.
Je, n8n ya kujiendesha yenyewe inafanya kazi?
Ndiyo, ikiwa URL yake ya Production ni HTTPS ya umma. easyCoexistence hukataa anwani za http, localhost, za faragha na za ndani unapohifadhi URL, na tena kabla ya kila wito, na haifuati uelekezaji upya.
Endelea kusoma
Uko tayari kuanza?
Sanidi WhatsApp Coexistence kwa dakika chache, si miezi. Programu inaendelea kufanya kazi kwenye simu.
Anza kipindi cha majaribio bila malipoImethibitishwa kwenye