Generic webhook
Plug Janore into anything that can POST JSON.
Zapier. Make. n8n. Pipedream. A Bash script on a Raspberry Pi. The webhook channel is the universal back door.
When to use it
- You're already orchestrating with Zapier or Make and want Janore as one step.
- You run an n8n or Pipedream workflow and need a smart-reply node.
- You have a custom backend and prefer a dead-simple shared-secret webhook over OAuth.
- You want to test Janore from
curlwithout generating an API key.
1. Enable the channel
Open Dashboard โ Channels โ Generic Webhook โ Connect. Optionally set a verify token โ a shared secret you'll send as a Bearer header. Skip it for fully open access.
2. POST a message
POST https://janore.com/api/v1/channels/webhook/{ASSISTANT_ID}
Content-Type: application/json
Authorization: Bearer {VERIFY_TOKEN} (optional)
{
"session_id": "any-string",
"message": "Hello",
"language": "en"
}session_id is any stable string per user. language is optional โ Janore auto-detects if omitted. The Authorization header is required only if you set a verify token.
3. Response shape
{
"reply": "Hello! โฆ",
"suggestedActions": [
{ "label": "View pricing", "type": "link", "payload": "/pricing" }
],
"conversationId": "uuid",
"messageId": "uuid"
}Identical to the REST API shape โ drop-in compatible.
Zapier โ 4 steps
1
Trigger
Pick whatever fires the workflow โ a new lead in HubSpot, a row in Google Sheets, a Typeform submission.
2
Webhooks by Zapier โ POST
URL:
https://janore.com/api/v1/channels/webhook/{ASSISTANT_ID}3
Body (JSON)
session_id, message, language. Map the trigger fields in.4
Use the reply
Pipe Zapier's response into the next step โ Slack message, email, CRM note, anything.
Make.com โ 4 steps
1
Trigger
Any module โ Webhooks, Gmail, Airtable, Telegram, you name it.
2
HTTP โ Make a request
Method:
POST. URL: https://janore.com/api/v1/channels/webhook/{ASSISTANT_ID}.3
Body type โ Raw JSON
Same fields as Zapier:
session_id, message, language.4
Parse response
Toggle Parse response on, then Make exposes
reply as a typed value for downstream modules.Limits
Same as the REST API: 60 requests/minute per assistant. Higher tiers lift the cap โ see pricing. On 429, back off using the Retry-After header.