Triggers
Every workflow starts with a trigger. The trigger defines when and how the workflow begins.
Schedule Trigger
Run your workflow on a recurring schedule.
Schedule options:
- Daily — runs once per day at a specified time
- Weekly — runs on selected days of the week
- Monthly — runs on a specific day each month
- Custom (Cron) — use a cron expression for complex schedules
Configuration:
- Timezone selection (e.g., America/New_York, Europe/London)
- Email notifications on start, complete, or failure
- Enable/pause/delete schedules independently
See Schedules for detailed configuration.
Webhook Trigger
Start the workflow when an HTTP POST request is received.
Each webhook trigger creates a unique URL you can call from external systems.
Configuration:
- Webhook URL — auto-generated, unique per workflow
- Auth token — optional security token for the webhook
- Expected fields — define what data the webhook expects
- Field defaults — pre-populate payload fields with default values
Example call:
curl -X POST https://api.qomplement.com/api/webhooks/trigger/YOUR_TOKEN \
-H "Content-Type: application/json" \
-d '{"document_url": "https://example.com/invoice.pdf"}'
See Webhooks for detailed configuration.
Email Inbox Trigger
Start the workflow when an email arrives at your unique upload address.
How it works:
- Someone sends a document to your
@qomplement.comemail address - The attachment is received by qomplement
- The Email Inbox trigger fires
- The document flows through your workflow
Configuration:
- Select which upload address to watch
- Filter by sender (optional)
- Filter by subject (optional)
This is powerful for automating document intake from email. See the Email-to-Data Pipeline example.