Receipt-triggered automations

Receipt-triggered automations let you start an automation whenever a receipt is created or its status changes in SwiftFox. This turns financial activity into a trigger, so you can send payment confirmations, flag failed payments, update custom fields, or run delayed follow-ups based on what happened with a receipt.

Receipt-triggered automations are built on the same automation canvas as every other automation. The difference is that the trigger is a receipt rather than a form, custom field, address or contact detail change. Receipts sit within the Finance area of SwiftFox, so this trigger connects your finance activity directly to automated communications.

What you can do with a receipt trigger

• Trigger an automation whenever a receipt is created or its status changes.
• Route different receipt outcomes (for example, successful vs failed payments) down different paths using conditional branches.
• Run the standard automation actions — update custom fields, send an email, send a text message, create a task, manage categories, and apply time delays.
• Filter on detailed receipt attributes so each path matches a specific financial scenario.
• Insert receipt-specific merge field values into emails and text messages for accurate financial communications.

Receipt triggers always use conditional outcomes

When you choose Receipt as the trigger, SwiftFox shows the notification: "Trigger requires conditions. Conditional branches will be automatically added based on receipt statuses. Use filters such as line type to tailor actions for each status."

After you click Add trigger, an Add conditions (If/Then) step is created automatically with two default branches:

• Success
• Failed

These two outcomes form the base structure for a receipt-driven automation. You can rename them, customise their conditions, or add more.

Creating a receipt-triggered automation

1. Go to Automations in the left menu.
2. Click Create automation.
3. Click the Trigger automation node, choose Receipt, and click Next.
4. Note the notification indicating the trigger requires conditions.
5. Click Add trigger and review the two default branches that are created automatically — Success and Failed.

Editing and adding conditional outcomes

1. Select the three-dot (overflow) menu on the Add conditions (If/Then) step and choose Edit.
2. Review the default success and failure conditions.
3. Add additional outcomes with Add Outcome as required, and give each an Outcome Name.
4. Choose All conditions are met or One condition is met for each outcome.
5. Within each outcome, select Add Condition and configure the receipt-based Field / Modifier / Value filter you want for that path.

Available receipt filters

The Field dropdown for a receipt condition typically includes:

• Status — the receipt status (values such as successful, failed, refunded or replaced; the exact values depend on your account).
• Line type — for example Subscription, Payment, Donation, or Ticket.
• Subscription category
• Line comments
• Total amount
• Payment method
• Target Email Address
• Target Mobile Number
• Name / Full Name

The available fields can vary between accounts, and extend with your account's own configuration. Use a Modifier (such as include, contains or does not contain) and a Value to build each condition.

Adding actions to a receipt automation

1. Within a conditional outcome, click Add an action.
2. Select the action type you need, such as:
   • Send an email
   • Send a text message
   • Update custom fields
   • Create a task
   • Delay automation
3. Configure the action as normal.

Using receipt merge fields in emails and text messages

When you configure an email or text message action in a receipt automation, receipt-specific merge field values become available.

1. In the message editor, type the @ symbol.
2. Select from the available receipt merge field values.

Typical receipt merge field values include receipt status, subscription category, line comment, total amount, payment method, receipt number, transaction reference, line type, date created, effective date and recipient email. The exact set can vary with how the account is configured.

How receipt automations fit together

• Receipt automations integrate with the Finance and Receipts system in SwiftFox.
• Conditional outcomes mirror real-world financial scenarios, such as successful and failed payments.
• Receipt merge field values align with the receipt data used in reporting and exports.
• Receipt automations can be combined with other automation logic and actions to build a complete journey.
• Common uses include payment confirmations, failed-payment notices, donor acknowledgements, and subscription workflows.

FAQs

What triggers a receipt automation?

Any receipt event that matches the conditions you have configured.

Do receipt automations require conditions?

Yes. Receipt triggers always build around conditional outcomes.

Can I trigger different actions for failed and successful payments?

Yes. Default Success and Failed outcomes are created automatically and can be customised or expanded.

What receipt details can I filter on?

Status, line type, subscription category, line comments, total amount, payment method, and target/name fields — and the set can extend with your account's configuration.

Can I personalise emails and text messages using receipt data?

Yes. Receipt-specific merge field values are available in both email and text message actions (type @ to insert them).

What is this feature commonly used for?

Payment confirmations, failed-payment notices, donor receipts, and other finance-driven workflows.