Developers
Help desk and CRM integrations
Log replied tickets, solved tickets, answered calls and handled conversations per agent from Zendesk, Intercom, HubSpot or any system, and optionally push online/offline status back.
How it works
Under Settings → Integrations → Help desks and CRMs an admin adds a connection, which gets its own endpoint URL. The help desk sends an event each time an agent replies to a ticket, solves one or answers a call. TINIUN checks the sender’s signature, finds the agent by work email, and adds one entry per event to the interaction log. Events are counted once even if the sender retries. See the result on the Interactions page, in the API (/v1/interactions), over MCP and in interaction.recorded webhooks.
Note
Zendesk
Log replied and solved tickets and answered calls per agent, and optionally set Talk availability from TINIUN status.
Setup
- In Zendesk, open Admin Center → Apps and integrations → Webhooks → Create webhook. Choose “Trigger or automation” as the connection method.
- Set the endpoint URL to the address shown below, method POST, format JSON, authentication “None”. Save.
- Open the webhook and copy its signing secret (Actions → Show signing secret). Paste it into the field below and save the connection.
- Create a trigger for each kind of event (for example “public comment added by an agent”). Add the action “Notify by → Active webhook”, pick this webhook and paste the matching JSON body shown below.
- Placeholder names come from Zendesk’s placeholder reference; check each one against your Zendesk version when you build the trigger.
Signature check: the X-Zendesk-Webhook-Signature HMAC over timestamp and body, with the signing secret you paste from Zendesk.
Body to send
One of these per kind (Ticket replied, Ticket solved, Call answered). agentEmail, externalId and occurredAt are required; channel, durationSec and reference are optional.
{
"kind": "ticket_replied",
"externalId": "{{ticket.id}}-ticket_replied-{{ticket.updated_at_with_timestamp}}",
"agentEmail": "{{current_user.email}}",
"occurredAt": "{{ticket.updated_at_with_timestamp}}",
"channel": "{{ticket.via}}",
"reference": "{{ticket.link}}"
}Intercom
Log conversations each teammate replied to or closed, and optionally set their away mode from TINIUN status.
Setup
- In Intercom, open Settings → Integrations → Developer Hub and create or open an app. Under Webhooks, set the endpoint URL to the address shown below.
- Subscribe to the topics “conversation.admin.replied” and “conversation.admin.closed”. Save.
- Copy the app’s client secret (Basic information) and paste it into the field below; Intercom signs each request with it.
- Make sure each teammate’s Intercom email matches their TINIUN work email.
Signature check: the X-Hub-Signature (sha1=…) over the body, keyed with your Intercom app’s client secret.
Intercom sends its own payload; TINIUN reads the conversation.admin.replied and conversation.admin.closed topics and takes the teammate from the latest admin conversation part. The teammate’s email must be present in the event.
HubSpot
Log calls and ticket replies per agent from HubSpot workflows.
Setup
- In HubSpot, build a workflow on the object you want to count (for example calls or tickets) and add the action “Send a webhook”.
- Use method POST and the URL shown below. Add a request header named X-TINIUN-Secret with the secret shown below (if your workflow action cannot send a custom header, send it through a relay such as your automation platform and let that add the header).
- Use the JSON body shown below, inserting HubSpot properties for the agent’s email and the record id.
- HubSpot’s own webhook subscriptions don’t cover calls, which is why workflows are used.
Signature check: either TINIUN-Signature: t=…,v1=… (the same scheme as TINIUN webhooks) or the shared secret in X-TINIUN-Secret over HTTPS. TINIUN generates the secret and shows it once.
Body to send
One of these per kind (Ticket replied, Ticket solved, Call answered). agentEmail, externalId and occurredAt are required; channel, durationSec and reference are optional.
{
"kind": "ticket_replied",
"externalId": "<record id>-ticket_replied",
"agentEmail": "<owner or agent email>",
"occurredAt": "<activity date as ISO 8601>",
"reference": "<record URL>"
}Any other system
Send events from any help desk, CRM or script. Signed like TINIUN’s own webhooks.
Setup
- POST JSON to the URL shown below, one event or {"interactions":[…]} with up to 100.
- Sign each request: send TINIUN-Signature: t=<unix seconds>,v1=<hex HMAC-SHA256 of "t.body" with the secret>, or send the secret itself in X-TINIUN-Secret over HTTPS.
- Repeating an externalId is safe; it is counted once.
Signature check: either TINIUN-Signature: t=…,v1=… (the same scheme as TINIUN webhooks) or the shared secret in X-TINIUN-Secret over HTTPS. TINIUN generates the secret and shows it once.
Body to send
One of these per kind (Ticket replied, Ticket solved, Conversation replied, Conversation closed, Call answered, Chat handled). agentEmail, externalId and occurredAt are required; channel, durationSec and reference are optional.
{
"kind": "ticket_replied",
"externalId": "your-unique-id",
"agentEmail": "[email protected]",
"occurredAt": "1970-01-01T00:00:00.000Z",
"channel": "email",
"durationSec": 0,
"reference": "https://…"
}Pushing online/offline status
For Zendesk and Intercom TINIUN can also push availability the other way: when an agent starts a break, goes into AUX or logs out, their Zendesk Talk availability or Intercom away mode is switched; when they are working again it is switched back. It only calls the vendor when availability actually changes, never delays an agent’s status change, and logs each call on the connection. It needs API credentials, which are stored encrypted and never shown again. Turn it on per connection, and use the Test buttons with one agent first.
- Zendesk: Sets the agent’s Zendesk Talk availability (phone) to available while working in TINIUN and unavailable on breaks, AUX and when offline. Needs an API token; the agent must have a Talk seat.
- Intercom: Turns a teammate’s Intercom away mode on when they are on a break, in AUX or offline in TINIUN, and off when they are working. Needs an access token with permission to update teammates.
What has and hasn’t been verified
Read this before relying on it
generic sender and the REST API always work.See it with your own scenarios
A 30-minute walkthrough with our team, tailored to your operation.
Book a demo
