Many finance workflows receive inputs by email: invoices, vendor reminders, or bank notifications. A human may currently classify the message and start the next step.
A configured `email_received` trigger can start an approved workflow after a matching message arrives. Review, connector, security, and exception-handling requirements remain in force.
5 Workflow Trigger Types
The workflow schema describes five trigger categories; availability and behavior must be verified in the target deployment:
Manual — click 'Run Now' in the dashboard. Good for ad-hoc processing or testing.
Schedule — cron-based recurring execution. Example: run bank reconciliation every morning at 9 AM.
Webhook — external HTTP POST triggers the workflow. Ideal for integrating with payment gateways, ERPs, or CRMs.
Email Received — matches incoming emails by subject keyword. Example: any email with 'invoice' or 'payment' in the subject triggers the AP processing pipeline.
API Event — internal event routing. Example: when a lead status changes to 'qualified' in your CRM, trigger the outreach sequence.
How Email Triggers Work
1. Configure the trigger with keyword filters: `{"filter": {"subject_contains": ["invoice", "payment"]}}`
2. Configure a supported, authorized inbox connector
3. Verify that a matching message creates the expected event and that unmatched or malicious messages are rejected
4. The first agent in the workflow receives the email content as input
5. The agent processes (extract invoice data, validate GSTIN, 3-way match) and passes output to the next step
6. HITL gates pause for human approval on high-value transactions
Illustrative Example: Invoice Preparation Pipeline
A hypothetical flow can classify an `invoice` email, extract fields, check GSTIN data through an authorized source, compare the invoice with a PO, request HITL approval under tenant policy, and prepare a ledger handoff for a supported connector.
Measure end-to-end time, reviewer effort, extraction and match quality, connector failures, and audit coverage during the pilot; no speed or zero-touch outcome is implied.
Connector Configuration
The connector configuration UI may expose authentication mode, secret references, base URLs, and health checks for supported adapters. Each adapter's fields, credential rotation, connectivity test, and production readiness must be verified individually.
Topics
Ready to try it?
Explore the public playground, or create an account to evaluate an agent with your own approved data and controls.