How do I choose and configure a workflow trigger?

Last updated: November 5, 2026

Every Whippy workflow begins with one trigger. Choose the trigger that best matches the event that should start the automation and the data later steps need.

Before you start

  • Decide whether the workflow should start from a webhook, email, schedule, or supported app event.

  • Have representative test data available before configuring later steps.

  • Treat webhook URLs and connected credentials as sensitive.

Trigger types

  • Webhook Request: Use when another system can send an HTTP request to Whippy.

  • Email Parser: Use when an incoming email should start the workflow.

  • Schedule: Use when the workflow should run repeatedly at a specific time.

  • Supported App Trigger: Use when a connected app exposes the event you need.

Steps

  1. Create or open a workflow draft.

  2. Click the empty trigger slot.

  3. Select the trigger type.

  4. Complete Setup.

  5. Complete Configure when additional fields are available.

  6. Open Test.

  7. Generate or load realistic sample data.

  8. Review the fields returned by the trigger.

  9. Save the trigger.

  10. Add the next workflow step.

Tips

  • 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.

  • Prefer an app trigger over a custom webhook when a native integration already supplies the event and fields you need.

Troubleshooting

  • If no webhook sample appears, copy the URL again and inspect the source system's delivery response.

  • If email does not start the workflow, confirm the parser address and publish status, then send a new test email.

  • If a schedule runs at the wrong time, review all five cron fields and the selected timezone.

  • If an app trigger is unavailable, confirm that the integration is enabled and supports the event.

  • If later steps cannot find trigger fields, test the trigger with a real sample and reopen the later step.