INTEGRATION GUIDE
Send workflow events securely.
Each workflow receives a unique bearer token when it is created. Keep the token in your automation platform's secret store. Do not put it in browser code, public repositories, or logs.
1. Start a run
Send the configured start event before or when the business process begins. Use a stable run ID to correlate its start and completion.
curl -X POST 'https://app.frontpilotai.com/api/events/WORKFLOW_ID' \
-H 'Authorization: Bearer WORKFLOW_TOKEN' \
-H 'Content-Type: application/json' \
--data '{
"event_key": "workflow.started",
"event_id": "unique-source-event-001",
"run_id": "order-12345",
"payload": {"source": "your-automation"}
}'2. Report completion
When the expected outcome is verified in the source system, send the configured completion event with the same run_id and a new unique event ID.
curl -X POST 'https://app.frontpilotai.com/api/events/WORKFLOW_ID' \
-H 'Authorization: Bearer WORKFLOW_TOKEN' \
-H 'Content-Type: application/json' \
--data '{
"event_key": "workflow.completed",
"event_id": "unique-source-event-002",
"run_id": "order-12345",
"payload": {"result": "verified"}
}'3. What happens next?
- Events require a valid per-workflow bearer token.
- Repeated event IDs for the same workflow are safely ignored.
- If a run passes its configured deadline without a completion event, the exception engine opens an exception.
- A late completion event resolves the corresponding exception and is recorded.
- Exception records and event history are stored in PostgreSQL. Sensitive payloads should not be sent unless needed and approved.
Important: FrontPilotAI does not connect to your CRM, payment system, or automation platform automatically yet. Configure the webhook in a system you control. This event monitor is not an AI agent and does not execute repairs or irreversible actions.