Test a workflow

How to test a PayFacile workflow before using it in production: activate, trigger a test order, check runs, and verify sent actions.

Why test your workflows

Before letting a workflow run in production, verify that it works as expected. A poorly written email, a webhook pointed at the wrong URL, or a delay that is too short can create a bad experience for your customers.

Testing means activating the workflow, triggering the event, then verifying that each action executed correctly.

Step 1: Activate the workflow

Open your workflow and activate it using the toggle at the top of the page. An inactive workflow does not execute any action, even if the trigger event occurs.

Step 2: Trigger the event

Create a test order on your store. Use a real payment method in test mode (if Stripe is in test mode) or place a real order with a small amount.

The "New order" or "Payment received" event fires, which starts your workflow.

Step 3: Check the runs

Go back to the detail page of your workflow in Marketing → Workflows. You will see the list of runs with their status: in progress, completed, or failed.

Click on a run to see the details of each action: email sent (with recipient), webhook sent (with response), pending delay.

Step 4: Verify the results

For emails: check your inbox (or the test customer’s inbox). The email should have arrived with the correct subject and content.

For webhooks: check in your external tool (n8n, Zapier) that the request was received with the correct data.

Deactivate after testing

If you are not yet ready to use the workflow in production, deactivate it after your tests. You can reactivate it once everything is validated.

Tip: to test long delays (3 days, 7 days), temporarily set short delays (5 minutes) during testing, then restore the real delays before activating in production.

FAQ

Do test runs send real emails?
Yes. An active workflow sends real emails. Use your own email address as the test customer to verify delivery.
How do I test a workflow with the "Payment failed" trigger?
In Stripe test mode, use card number 4000 0000 0000 0341 which simulates a decline. This generates the "Payment failed" event and triggers the workflow.
Was this helpful?