Send TikTok Lower Funnel Event

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Send TikTok Lower Funnel Event under Add Steps.

Before you start

• An owner, admin or agent can add this step and save the workflow. Publishing that workflow — the thing that makes it run on live conversations — is an owner or admin action.
• Building and running workflows depends on your plan; see pricing.
• A TikTok ads account connected in Settings → Integrations unlocks this step's fields in the drawer — but connecting one does not make the step send anything; see Limits.

Set up

1. Open the workflow and click + where the event would belong.
2. Pick Send TikTok Lower Funnel Event.
3. Choose an event under Event — Place an Order, Complete Payment, Submit Form, Cancel an Order, Disqualified Conversation or Spam.
4. Optional: set Value and Currency.
5. Saving and publishing the workflow both succeed — running it does not; see When it fails.

Fields

Event

TikTok's own lower-funnel names: Place an Order, Complete Payment, Submit Form, Cancel an Order, Disqualified Conversation, Spam.

Value

The order or payment amount, as a number or a placeholder.

Currency

A 3-letter ISO code for Value.

How it works

• What would leave Inchat, if it sent anything: the event name, the amount and currency when both resolve, and an identifier for this conversation. Today, nothing leaves Inchat at all — the step's sender is a stub that always reports the same failure, regardless of the event, the amount, or whether a TikTok ads account is connected.
• Connecting a TikTok ads account under Settings → Integrations unlocks this step's fields in the drawer, because that connection is what the TikTok Messaging Ads trigger checks for. Sending a lower-funnel event needs a separate advertiser authorisation with TikTok's own Events API, which no workspace holds — so the step fails the same way whether or not a TikTok ads account is connected.

When it fails

• Every run: the step fails with TikTok lower-funnel events are not connected in this workspace, with nothing sent.
• A failed event does not stop the run: the step is recorded failed and the flow moves straight to the next one, so anything placed after it still happens.

Limits

• It cannot send an event today. Treat this step as a placeholder for a capability that is not built yet, not a working integration — do not rely on it for ad attribution.
• It publishes even with nothing connected, and even once connected it still fails every run — the connection card in the drawer only gates the fields, not whether the send can succeed.
• There is no way to make it send today; the only fix is Inchat wiring up TikTok's Events API, not a workspace-side setting.
• Use Send Conversions API Event for Meta attribution instead — that one is a real, working integration.

Related

• Send Conversions API Event — Report a conversion — a lead, a purchase, a cart — to Meta's Conversions API from this conversation's channel, so ad optimisation can see what happened after the click.
• HTTP Request — Call an outside API over HTTPS and keep its response for later steps and conditions. Two things to know before using it today: placeholders in the URL and body are not resolved, and production had no host on its outbound allow-list at the time of writing — see Limits.
• Workflows: how a flow runs — A workflow is one trigger, optional conditions and an ordered list of steps; only a published workflow runs, and this article explains how a run starts, forks, pauses, fails and stops.