Intercom
A read token from the Developer Hub. Conversation JSON paths were not re-fetched.
What you can track
New and open conversations and first response time, after test_job shows the fields. This playbook does not invent a conversation JSON path.
Credential
An access token from a Developer Hub app, with only Read permissions (conversations, and admins or tags only if you need them). Bearer.
Host: api.intercom.io. Suggested name: INTERCOM_TOKEN.
Where to get it
Settings → Integrations → Developer Hub → create “tlly” → Authentication → read permissions → copy the token. Authentication.
tlly job
Preview a GET, then lock the extract to the keys you see. The URL below is the host the members-area guide uses; the path is unverified:
{"series":"intercom_conversations","cron":"0 7 * * *","request":{"url":"https://api.intercom.io/conversations","headers":{"Authorization":"Bearer {{secret:INTERCOM_TOKEN}}","Accept":"application/json"}},"extract":{"format":"json","items":"conversations","date":"created_at","aggregate":"count"}}
Change items and date to match the preview. Intercom pages with a cursor. tlly will not follow it.
Gotchas
- Leave every write permission off.
- Conversation bodies are personal data. Count them; do not store the text.
- A version header (Intercom-Version) is commonly required and was not re-read on the authentication page. If the preview says the version is missing, add the header the error names.
Alert ideas
Red when open conversations (once the field is real) exceed the team’s ceiling. Yellow when the newest conversation is older than a day (a stale series, or a count of zero new ones).
Verification
The token steps match the members-area Intercom guide and the authentication doc it links. The /conversations path and field names in the sample are unverified.