14

Workflows

Last Update kaksi päivää sitten

Getting started with Workflows Creating your first workflow, step by step Choosing what triggers a workflow Building workflow steps: actions, conditions, waits and AI steps Using runtime data in workflows

Adding leads to Notion with workflows

Do you keep your leads or requests in a Notion database? A workflow can add a new row to it, for example each time your AI agent finds a lead.

tawk.to has no Notion step, so you connect the two yourself. In Notion, you create a connection and share your database with it. In tawk.to, an HTTP request step sends each new row. You copy a token, an ID and a short template, and you do not write code.

Time: about 30 minutes.

What you can and cannot do
You canAdd a new page (row) to a Notion database and fill in its properties, for example name, email address, company and need.
You cannotFind or update a row that already exists. Each run adds a new row, so the same person can appear twice. You also cannot put the visitor's name, email address or chat messages straight into the row: they must come from your AI agent or an AI step (see What you can put in the row below).
You needThe property admin role in tawk.to, a Notion Workspace Owner to create the connection, and a Notion database for your leads. On Notion Business and Enterprise plans, the owner may first have to allow connections in the workspace settings.
This guide uses a database with these properties. Yours can have other names, but then change them in the template in step 4.
PropertyType in Notion
NameTitle
EmailEmail
CompanyText
NeedText

Step 1: Create a Notion connection

  1. Follow Notion's guide Create an internal Notion connection. Name the connection, for example tawk.to, and select your workspace.
  2. Copy the connection's API token.
Important: The token can open every page that you share with the connection. Keep it private.

Step 2: Share your database with the connection

  1. In Notion, open your database.
  2. Click … in the top-right corner.
  3. Click Connections.
  4. Add the connection from step 1.
For more, see Notion's guide Add and manage connections with the API.

Step 3: Copy the data source ID

  1. In your database, open the settings menu.
  2. Click Manage data sources.
  3. Click the menu next to the data source.
  4. Click Copy data source ID.

Step 4: Add an HTTP request step in tawk.to

  1. Open your workflow in Automations > Workflows.
  2. Click Add step.
  3. Click Action.
  4. In Category, select Developer tools.
  5. In Action, select HTTP request.
  6. In URL, type https://api.notion.com/v1/pages.
  7. In Method, select POST.
  8. Under Headers, click Add header two times and fill in the two headers from the table below.
  9. In JSON body, paste the template below.
  10. Replace YOUR-DATA-SOURCE-ID with the ID from step 3.
  11. Click Save.
Header nameHeader valueSecret
AuthorizationThe word Bearer, a space and your API tokenOn
Notion-Version2026-03-11Off
Turning on Secret hides the token after you save. tawk.to sends secret headers only to https:// addresses.
The template must match your database exactly:
  • Names: each property name, for example "Name" or "Email", must be the same as in your database, capital letters included.
  • Types: each property needs its type: title for the Title property, email for an Email property and rich_text for a Text property.
  • Length: a Text property holds up to 2,000 characters.
Note: The JSON body must be valid JSON, or you cannot save the step. Keep each {{ }} value inside quotation marks, as in the template. tawk.to inserts the details safely, even when they contain quotation marks or line breaks.

What you can put in the row

Workflow starts fromWhat you can useExample
Your AI agent (AI agent trigger)The details that the agent collects{{trigger.name}}, {{trigger.email}}, {{trigger.need}}
A chat (for example Chat transcript created)The output of an AI step that summarizes the chat{{nodes.<step ID>.output}}
A website form (Webhook trigger)The fields that your form sends{{trigger.email}}
A webhook request must be signed, so a website form usually needs a developer to send it. See Choosing what triggers a workflow.

Why chats need an AI step: the visitor's name, email address and chat messages are private details. An HTTP request cannot send them, because only Slack steps and conditions can use them. An AI step can read them and write a summary, which you put in a Text property.

The template above uses the details that the Qualified lead hand-off template collects. To build on it, add the HTTP request step to that template. If you do not also want a deal in tawk.to, delete its Create card step. For more about deals, see Creating deals from chats with workflows.

For every detail you can use, see Using runtime data in workflows.

Step 5: Test it

  1. In the Settings tab, turn on Enabled and click Save.
  2. Click the Runs tab.
  3. Click Run now.
  4. In Trigger data (JSON), change the sample values to a test name and email address.
  5. Click Run now.
  6. Check your Notion database for the new row.
  7. Click the run to see the result.
If the step failed, Notion's response in the run tells you why.

Important: Run now starts a real run, so every step in the workflow runs.

If it does not work

What you seeWhat to do
Status 400A property name or type does not match your database. Read Notion's message in the run, then fix the JSON body.
Status 401The API token is wrong or was refreshed. Copy the token again and enter it in the Authorization header.
Status 404The database is not shared with the connection, or the data source ID is wrong. Repeat step 2 and step 3.
Status 429Notion received too many requests. Try again later.
By default, any status outside 200 to 299 fails the step and stops the run. If later steps should still run, turn on Continue even if the request fails in the step. Later steps can then check the HTTP status.

For more about runs and errors, see Testing, monitoring and troubleshooting workflow runs.

Good to know

  • Copies lose the token. A copy made with Duplicate does not include secret headers, so the Authorization header is gone. Add it again, with Secret on, before you turn on the copy.

Related guides

Have a question we haven't covered or need support?

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us