Workflow Trigger

Entry point for sub-workflows, manual or API starts, and handoffs from a parent bot.

The Workflow Trigger marks where a target workflow (bot) begins when it is started outside a normal customer Pingmee Trigger event. The sidebar form has no trigger-specific fields—only the shared Description field available on all nodes.

When to use

Use Workflow Trigger instead of Pingmee Trigger when the bot should not start from an inbound customer message alone:

Manual or API start — You send the bot to customers yourself (from Pingmee) or start it via the API.
Parent bot handoff — A parent workflow starts this bot using Workflow Pointer (sub-bot or modular flow).

Also use it for:

Every sub-workflow callable via Workflow Pointer (ticketing, CRM update, escalation playbook).
Keeping a parent flow readable by delegating a block of steps to a separate published workflow.

Configuration

Field	What it does	When to use
Description	Optional text on the node card	Explain what this sub-workflow expects or returns

There is no platform, keyword, or post selector on this trigger. Configure behavior in the target workflow’s first actions after this node.

Flow behavior

Input: No incoming connections (trigger).
Output: One outgoing edge to the rest of the target workflow.
Pairing: The calling workflow’s Workflow Pointer must select this workflow’s id in Select Workflow To Run.

Examples

Callable “assign and notify” module

Create workflow Support handoff starting with Workflow Trigger.
Chain Update Conversation (agents/tags) → WhatsApp notification.
In the main workflow, add Workflow Pointer and select Support handoff.

Document the contract

Select Workflow Trigger.
In Description, note required upstream context (for example, “expects conversation id from pointer”).

Pingmee Trigger — customer-initiated conversations on connected channels
Workflow pointer (concept)
Workflow Pointer
Documentation home