> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trytikt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> When a lead matches your filters for the first time: add it to a list, send it to your tool, notify you.

A **workflow** says, in one sentence: *when a lead matches these filters for the first time, add it to a list, send it, let me know.* You create it on the **Leads** page, with the **Workflows** button — or from a destination, with **Create workflow** — and it runs on its own.

## When it runs

A workflow checks each lead **when it is scored, and each time it comes back** (a new reaction or comment). The first time the lead matches its filters, the workflow runs its actions — **once per lead, for the workflow's whole life**: a lead who engages again doesn't go back to your CRM.

* A lead you discarded is never sent.
* Changing a workflow's filters applies to the leads that come next, not to the ones it already passed.
* A lead can match two workflows: each one runs its actions.

The filters are described in [Filters](/webhooks/filters): score, each ICP criterion (Met / Not met), **Engaged by** (reactions, comments or both), **At least** a number of engagements, tracked profiles.

## The three actions

A workflow has one to three actions, at most one of each kind. They run together.

| Action | What it does |
| - | - |
| **Manage lists** | Adds the lead to a list. The lead is marked **auto** and stays in your working view until you handle it. |
| **Send notifications** | An email to the workspace owner, or a message in a Slack channel — **one per batch of new leads**, never one per lead: at most one every 4 hours per workflow, listing up to 10 leads and how many more. |
| **Send webhook** | Sends a [`lead.matched`](/webhooks/events/leads) event to one destination, signed, in its format. |

### `lead.matched`

```json theme={null}
{
  "id": "…",
  "type": "lead.matched",
  "created_at": "2026-10-06T08:12:31Z",
  "api_version": "2026-10-01",
  "workspace_id": "…",
  "data": {
    "workflow": { "id": "…", "name": "Hot CFOs", "reason": "new" },
    "lead": { "…": "the complete lead" }
  }
}
```

* `workflow.reason` says why the lead arrives: `new` (a new lead), `came_back` (it engaged again and now matches), `rescored` (its new score matches), `past` (it already matched when you first turned the workflow on).
* It goes **only** to the destination chosen in the workflow — never to a destination listening to **All events**, and you can't subscribe to it. A destination can listen to no event at all and only receive its workflows.
* A complete example is on the [lead events page](/webhooks/events/leads).

## Turning it on

**Turn on** starts the workflow right away. The first time, a box — checked by default — also applies it to **the leads of the last 30 days that already match**: TIKT adds them to the list and sends them to your destination within minutes, with the reason `past`. They are **never notified**: no email or Slack message for old leads.

| What happens | Effect |
| - | - |
| You pause the workflow, then turn it back on | It starts again from now: what happened during the pause is not caught up. |
| Its destination is off or turned off by TIKT | Its `lead.matched` events wait; they are sent when the destination is back on. |
| Its list or its destination is deleted | The workflow is paused, and says why. |
| You edit its filters | The new filters apply to the next leads. |

A workspace has up to **20 workflows**, drafts included. Each workflow's **Activity** tab shows the last 30 days: every lead it passed, why, and what each action did.

## Slack

**Send notifications › Slack › Connect Slack** opens Slack's own page: you pick the channel and click **Allow**. TIKT gets an address to post in that channel — nothing else: no access to your messages, your people or your other channels. A welcome message is posted right away. See the [Slack guide](/guides/slack).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.