Why it matters
Every workflow begins with one trigger. Choosing the correct trigger determines when the automation starts and what data is available to later steps. A reliable trigger prevents missed events, duplicate runs, and workflows that start at the wrong time.
Key Concepts
Trigger: The first step in a workflow and the event that starts a run.
Trigger Payload: The data supplied by the triggering event.
Sample Data: Example trigger data used to configure and test later steps.
Webhook: An HTTP request sent to Whippy by another system.
Email Parser: A workflow email address that converts an incoming email into structured data.
Schedule: A recurring time defined with a five-field cron expression and timezone.
App Trigger: An event exposed by a supported connected app.
Subscription: A connection that listens for events from an external app, sometimes created when the workflow is published.
Available Trigger Types
Webhook Request
Use Webhook Request when another system can send an HTTP request to Whippy. The request body becomes data that later steps can use.
Common uses include receiving an ATS update, processing a form submission, or starting a workflow from a custom internal system.
Email Parser
Use Email Parser when an incoming email should start the workflow. Whippy provides a workflow email address and normalizes email information such as the sender, recipient, subject, body, and available attachments.
Common uses include routing inbound requests, extracting information from structured emails, saving attachments, or generating summaries.
Schedule (Cron Expression)
Use Schedule when the workflow should run repeatedly at a specific time. Configure a five-field cron expression and the intended timezone.
Common uses include daily summaries, weekly reports, recurring synchronization, and periodic checks.
Supported App Trigger
Use an app trigger when a connected app exposes the event you need. Available apps and trigger events depend on the integrations enabled for your organization.
Examples can include a meeting being booked, a page changing, or a record being created in a connected system.
Choose the Right Trigger
Choose Webhook Request for real-time events from systems that can send webhooks.
Choose Email Parser when email itself is the source data.
Choose Schedule when the process should run at a predictable recurring time.
Choose an app trigger when Whippy provides a native trigger for the connected product.
Prefer an app trigger over a custom webhook when the native integration already supplies the event and fields you need.
Configure and Test a Trigger
Step-by-Step: Add a Trigger
Create or open a workflow draft.
Click the empty trigger slot.
Select a trigger type.
Complete Setup.
Complete Configure when additional fields are available.
Open Test.
Generate or load realistic sample data.
Review the fields returned by the trigger.
Save the trigger.
Add the next workflow step.
Test a Webhook Trigger
Add Webhook Request as the trigger.
Copy the webhook URL shown by Whippy.
Send a test request from the source system or an API testing tool.
Return to Test in the workflow builder.
Confirm the sample payload appears.
Review field names and nested objects.
Save the trigger.
Keep the webhook URL private. Anyone able to call it may be able to start the workflow.
Test an Email Parser Trigger
Add Email Parser as the trigger.
Copy the workflow email address.
Send a representative email to that address.
Include a safe attachment if the workflow will process attachments.
Return to the trigger’s Test tab.
Confirm the sender, subject, body, and attachment data appear.
Save the trigger.
Use a representative email format. Later variable mappings depend on the fields produced by the test.
Configure a Scheduled Trigger
Add Schedule (Cron Expression).
Enter a valid five-field cron expression.
Select the correct timezone.
Review the described schedule.
Test the trigger configuration.
Save and publish the workflow.
Document the intended schedule in the workflow description so teammates do not need to interpret the cron expression.
Configure an App Trigger
Select the supported app in the trigger picker.
Connect or choose the account Whippy should use.
Select the trigger event.
Complete the app-specific fields.
Test or load a sample event.
Review the returned data.
Save and publish the workflow.
Confirm the external subscription is active when the app requires one.
Tips and Best Practices
Use the most specific trigger available for the event.
Test with data shaped like real production events.
Apply a filter immediately after the trigger when only some events should continue.
Set the timezone explicitly for scheduled workflows.
Avoid sending the same event through multiple triggers unless duplicate runs are intentional.
Re-test the trigger after changing the source system’s payload or permissions.
Treat webhook URLs and connected credentials as sensitive.
Troubleshooting
Issue | Possible Cause | Fix |
No webhook sample appears | The request used the wrong URL or did not reach Whippy | Copy the URL again and inspect the source system’s delivery response |
Email does not start the workflow | It was sent to the wrong parser address or the workflow is unpublished | Confirm the address and publish status, then send a new test email |
A schedule runs at the wrong time | The cron expression or timezone is incorrect | Review all five cron fields and select the intended timezone |
An app trigger is unavailable | The integration may not be enabled or may not offer triggers | Check available apps and confirm that the selected app supports the event |
An app trigger stops receiving events | The account or webhook subscription may no longer be valid | Reconnect the account and republish or recreate the subscription as required |
Later steps cannot find trigger fields | The trigger has no representative sample data | Test the trigger with a real sample, then reopen the later step |