Skip to main content
There are two ways to follow what happens in your workspace. Most integrations use the first; the second is the safety net. Both carry the same events, in the same envelope: the same id, type, created_at and data. A sync can mix them — receive webhooks, and read the log after an outage to fill the gap.

​
Read the event log

The first time, start from a date:
Events come oldest first, up to 100 per page (limit), with the usual pagination. Keep the id of the last event you handled: next time, ask for what comes after it.
What the log guarantees:
  • In the order TIKT wrote them, and never one skipped: an event appears only once everything written before it is complete. The price is a delay of a few seconds at most.
  • 180 days of history. lead.matched (a workflow match) is in the log; test events are not.
  • data is the object as it is now, like a resend: a lead read today has today’s score.

​
Follow new engagements

To know who engaged with which post — every reaction and comment of your leads — read the engagement feed, oldest first, from a date:
Each item is { "lead_id", "signal" }: the lead, and the engagement with its post and tracked profile. Filter with kol_id, post_id, or kind (reaction, comment, reply). Only engagements of your leads are there, never those of people who aren’t.

​
Example: keep a CRM up to date

A scenario that runs every 15 minutes:
  1. Read the bookmark you saved last time — the id of the last event handled.
  2. GET /v1/events?after=<bookmark>&type=lead.created,lead.status_changed,list.lead_added, page after page until has_more is false.
  3. For each event, in order:
    • lead.created → create the contact from data.lead.person and data.lead.company;
    • lead.status_changed → when the lead was discarded, mark the contact;
    • list.lead_added → tag the contact with the list’s name.
  4. Save the id of the last event as the new bookmark — only after the CRM has accepted the changes, so a failed run starts again from the same place.
Then answer TIKT from the CRM: when a contact is marked as contacted, file the lead in a list with POST /v1/lists/{id}/leads — see Respond to TIKT in the n8n, Make, Zapier and Clay guides.