Actions
Automate email, webhook, and electronic invoice deliveries triggered by order events, payment milestones, schedules, or manual execution.
Actions automate communications in your workspace. Each action is an email, a webhook, or an electronic invoice -- you define what triggers it, who receives it (or which URL it calls), and what content or payload to include. Instead of manually sending confirmation emails, payment reminders, or notifying external systems, actions handle these automatically whenever their conditions are met.
How It Works
Each action pairs a delivery method (email, webhook, or electronic invoice) with one or more triggers. When a trigger fires -- whether from a system event, a schedule, or a manual click -- Itsy evaluates any conditions you have set. If the conditions pass, the action executes: for email actions the message is rendered with order data and sent to the configured recipients; for webhook actions a JSON payload is dispatched to the configured URL; for electronic invoice actions the issued invoice is transmitted through Peppol. All deliveries are tracked.
Editing Workflow
When you open an action from the list, you enter a tabbed detail view with four tabs:
| Tab | Purpose |
|---|---|
| Overview | Action identity, delivery settings, segments, and active status |
| Content | Rich text editor for designing the email body (email actions only) |
| Triggers | Configure event, schedule, and manual triggers with conditions |
| Deliveries | Send history for this action with status, timestamps, and event logs |
Each tab saves independently. You can update the content without affecting the triggers, and vice versa. See the Editing an Action page for a full walkthrough of each tab.
Key Concepts
Action Type
Every action has a type that determines how it delivers its message:
| Type | Description |
|---|---|
| Sends an email to one or more recipients. You configure the subject, body, sender, and attachments. | |
| Webhook | Sends an HTTP request with a JSON payload to an external URL. You configure the URL, secret, headers, and HTTP method. |
| Electronic Invoice | Transmits the issued invoice as a structured Peppol e-invoice. Available only when your workspace has the e-invoicing feature enabled. |
You choose the type when you create the action. All action types share the same trigger system -- the difference is only in how they deliver.
Action Properties
All action types share these core properties:
| Property | Description |
|---|---|
| Name | Internal name for the action |
| Code | A short identifier code |
| Color | A color label for visual identification across lists, deliveries, the dashboard, and order timelines |
| Segments | Which customer segments this action applies to. Leave empty to apply to all segments. |
| Active | Whether the action is currently enabled |
Email-specific properties:
| Property | Description |
|---|---|
| Subject | The email subject line (supports template variables) |
| Sender Name | The display name shown as the email sender |
| Sender Address | The email address it is sent from (defaults to workspace sender if empty) |
| Default Sender | Who manual sends start from: the workspace sender, or the person sending. See Operator Sender. |
| Recipients | Who receives the email, in any combination (see below) |
| CC / BCC | Additional email addresses to copy |
| Content | The email body, built with a rich text editor |
| Attachments | Files to include with the email |
Webhook-specific properties:
| Property | Description |
|---|---|
| Webhook URL | The HTTPS endpoint to call (must be a public URL) |
| Secret | A shared secret used to sign the payload with HMAC-SHA256 (required). The signature is sent in the X-Itsy-Signature header so the receiver can verify authenticity. |
| HTTP Method | The HTTP method to use: POST (default) or PUT |
| Custom Headers | Additional HTTP headers to include with each request. Reserved headers (X-Itsy-*, Content-Type, Content-Length, Host) cannot be overridden. |
| Max Attempts | The maximum number of delivery attempts, including the first attempt (default: 5). Failed deliveries retry with increasing delays. |
Trigger Types
Each action can have multiple triggers. There are three types:
| Type | Description |
|---|---|
| Event | Fires automatically when a specific system event happens (e.g., an order is confirmed or a payment is received) |
| Schedule | Runs on a daily schedule at 02:00, evaluating all orders against the trigger's conditions |
| Manual | Only fires when you explicitly run it from the order page |
An action can have any combination of triggers -- for example, you might have an action that fires both on the "Order Confirmed" event and can also be triggered manually from the order menu.
Available Events
Event triggers respond to 21 different system events:
| Category | Events |
|---|---|
| Order lifecycle | Order Created Internally, Order Created Externally, Order Placed, Order Confirmed, Order Cancelled, Order Completed, Order Locked |
| Payment | Payment Deposit Reached, Payment Fully Paid, Payment Validated from External Service |
| Invoice | Invoice Created, Invoice Voided, Invoice Updated |
| Notification | Notification Delivered, Notification Failed, Notification Bounced |
| Group | Group Message Created, Group Message Updated |
| Gift Certificate | Gift Certificate Created |
| Availability | Order Overbooked, Paid Order Blocked By Availability |
Order Placed
Order Placed fires when an order becomes a real order: when it leaves Draft for Pending or Confirmed. It is the event for a "thank you for your order" email. It fires once per order, so unlike a payment event it never confuses the payment a customer makes at checkout with a later payment on the same order.
It fires however the order leaves Draft:
- The customer pays at checkout. The payment gateway confirms the payment, and the order moves to Pending (deposit paid) or Confirmed (fully paid).
- Someone on your team moves the order on. For example, when a customer paid but the gateway's confirmation never arrived, or after you record a payment taken outside the gateway. The customer gets their confirmation at that point, unless your conditions leave it out.
It does not fire when:
- the customer leaves checkout without paying, so the order stays in Draft
- a Draft order is cancelled
- a later payment arrives, including the one that moves a Pending order to Confirmed
- a cancelled order is reinstated
- the order was never a Draft. Orders your team creates in the admin start in Pending, and group registrations start in Registered.
Payment events still fire for the payment that placed the order, so receipts and other payment actions are unaffected.
Two conditions are offered only on the Order Placed trigger:
| Condition | Values | Use it to |
|---|---|---|
| Placed As | Pending, Confirmed | Word a deposit confirmation differently from a full-payment one |
| Placed By | Verified payment, Manual | Leave out orders your team moved on by hand, or send only for them |
Combine them with Booking Source to thank only customers who booked online. For example, two actions on Order Placed:
| Action | Conditions |
|---|---|
| Deposit received | Placed As is Pending, Booking Source is Online |
| Booking confirmed | Placed As is Confirmed, Booking Source is Online |
No action is bound to Order Placed until you add one. If you already send an email on Order Created Externally, note that it fires when the customer starts checkout, before they pay, so it also reaches customers who never complete payment. Check that customers will not receive two emails within a minute of each other.
The order's timeline records each placed order. When a verified payment placed it, the entry links to that payment.
Manual Trigger Placements
A manual trigger places an action at an entry point on an order. Email actions are sent through one send panel, which lists only the actions placed at the entry point it was opened from, along with that entry point's managed template:
| Entry point | Opens the send panel from | Template |
|---|---|---|
| Order header | Send documents at the top of an order | Document Delivery |
| Invoice list | Send in an invoice's menu | Document Delivery |
| Payment reminder | Sending a payment reminder from the order | Payment Reminder |
| Payment receipt | Sending a receipt from a payment | Payment Receipt |
Each entry point is set to Off, Available (listed in the panel) or Default (the panel opens with it). The panel opens with the first of these that applies to the order:
- An action set to Default there that is limited to the order's segment
- An action set to Default there for every segment
- The entry point's template
The operator can still pick anything else in the list. If two Default actions apply to the same orders, the trigger editor warns about it, and the panel opens with whichever comes first by name.
An email action can also be placed in the Order action menu, the menu at the top of an order. This placement is set to Off or Available only. Every action set to Available appears in the menu as an item of its own, listed by name, so there is no default to choose. Picking one opens the send panel with that action selected, and the operator reviews the email, edits it if needed, and sends it. Nothing is sent on click. The items appear on orders in every status, including Draft, Cancelled and Completed. The Order action menu is separate from the Order header entry point, so an action set to Available in both appears in both.
A webhook action can be placed in the Orders top menu, where it appears as an entry that runs it. An electronic invoice action cannot: it needs an invoice to transmit, so it runs only on an invoice event.
Trigger Conditions
Conditions let you control exactly when a trigger fires. Each condition checks an order property against a value using a comparison operator. All conditions on a trigger must be satisfied for the trigger to fire (they are combined with AND logic).
Condition fields:
| Field | Description |
|---|---|
| Order Status | The current status of the order. Supports multi-value matching (is any of / is none of). |
| Total Price | The order's total price |
| Total Paid | The amount paid so far |
| Balance | The remaining amount owed (Total Price minus Total Paid) |
| Order Created | Days since the order was created |
| Start Date | Days relative to the trip departure date |
| End Date | Days relative to the trip return date |
| Fully Paid Date | Days since the order was fully paid |
| Deposit Due Date | Days relative to the deposit deadline |
| Payment Status | The payment status (No Payment, Needs Deposit, Needs Full Payment, Fully Paid) |
| Order Origin | Where the booking came from (Online, Internal, API, Partner) |
| Readiness Score | The order's numeric readiness score (0--100) |
| Readiness Status | The RAG status derived from the readiness score (Green, Amber, Red) |
| Questions Answered | The number of traveler questions that have been answered |
| Has Label | Whether the order has specific labels. Supports multi-value matching (has any of / has none of). |
| Placed As | Order Placed trigger only. The status the order was placed in: Pending or Confirmed. |
| Placed By | Order Placed trigger only. What placed the order: a verified payment, or manual. |
Comparison operators:
| Operator | Description |
|---|---|
| Is equal | Must match exactly |
| Is not equal | Must not match |
| Is larger than | Must exceed the value |
| Is smaller than | Must be less than the value |
For date conditions, the value represents a number of days relative to today. For example, setting "Start Date is equal to -7" matches orders whose trip starts 7 days from now. Multi-value fields (Order Status, Has Label) use "is any of" and "is none of" semantics instead of the standard operators.
A date condition can also hold several days, such as "56, 49, 42, 35, 28, 25, 20 days before Order Fully Paid Date". An order matches on each night it is exactly one of the listed days away from its date, so one scheduled action can send a whole series of reminders. All the days in one condition are either before or after the date. Days that have already passed when an order comes into scope, or that fall on a night the schedule did not run, are skipped rather than sent late. See Sending a reminder on several days for a worked example.
Condition Preview
When editing conditions on a trigger, you can click Preview to test them against the orders in your workspace. The preview behavior depends on the trigger type:
- Scheduled triggers -- The preview simulates a full schedule run. You pick a date, and Itsy shows which orders would be matched on that day, along with the reason each one passes. This is a forecast: the matched orders are exactly the ones the schedule would email on that run.
- Event triggers -- The preview shows which orders currently pass the conditions. Because an event trigger fires for a single order (the one that raised the event), the preview is a sanity check rather than a forecast -- it answers "do these conditions select the orders I expect?" rather than "how many emails will go out?"
Both modes list the matched orders with their condition results, so you can verify that your conditions produce the expected results before the trigger runs live.
Placed As and Placed By describe the moment an order was placed, which no existing order can answer. The preview lists them as checked when the event fires, and matches orders against your other conditions only.
Email Recipients
An email action sends to any combination of these recipients. Tick at least one.
| Recipient | Description |
|---|---|
| Client | The order's client (the billing entity). For corporate clients, Itsy routes to the appropriate contact based on context (invoice contacts for invoice-related actions, payment contacts for payment actions). |
| Primary participant | The order's primary participant |
| Other participants with an email | Every participant on the order other than the primary participant who has an email address |
| Group contact | The contact person of the order's group |
| Workspace admin | The workspace's sender address |
| Custom email | A specific email address you enter |
For example, an action can go to the primary participant and the workspace admin, without the client.
Each recipient gets an email of their own, so recipients don't see each other's addresses. CC addresses are the exception: they show on every copy. When two recipients share an address, that address gets one email. It is addressed to the first of them in the order of the table above: the client, then the primary participant, then other participants in the order they were added, then the group contact, the workspace admin and the custom address.
A selected recipient with no address is skipped without stopping the others: a client with no email, an order with no primary participant, or an order that isn't in a group. Each skip is noted on the order timeline. The action no longer falls back to the client when a group contact or custom address is missing; tick Client as well if the client should get it.
Every recipient gets the same attachments. You can also add CC and BCC recipients to any action; they get a copy of every email the action sends.
Use the recipient variables to greet each recipient by their own name. Client variables always show the client, in every copy.
Operator Sender
By default, action emails go out from the workspace sender -- the sender name and address configured on the action, or the workspace's own when neither is set. For manual sends, you can choose to send as the person who presses send instead. When the send dialog opens, the operator can switch between the workspace sender and their own address.
How it works:
- On the action's Overview tab, the Default sender for manual sends setting controls which option the dialog starts on: the workspace sender, or the person sending.
- The operator can change it for each email they send. The setting is a starting point, not a lock.
- Automated sends always go out from the workspace sender. The operator sender applies only to manual sends.
- An operator can only send as themselves when their email domain matches the workspace sender's domain. If it does not match, only the workspace sender is offered.
When an operator sends as themselves, their address appears as the From and Reply-To, and their display name appears as the sender name. Replies go to the operator, not to the workspace.
Email Content
The email body is built with a rich text editor that supports headings, paragraphs, bold, and italic formatting. You can insert special content blocks that are automatically populated with order data. Use the Insert Block dropdown in the editor toolbar to add them.
Information blocks:
| Block | Description |
|---|---|
| Order Code | Displays the order reference number prominently |
| Client Information | Shows the customer's name, email, phone, and address |
| Order Information | Shows trip name, participants, booking date, departure date, total price, balance, and bookings |
| Trip Information | Shows the trip name and departure date |
| Flight Bookings | Shows Amadeus air bookings linked to the order, grouped by PNR with flight segments, routes, departure and arrival times, class of service, and baggage allowance. Renders only when the order has Amadeus tickets; otherwise the block is omitted. |
Financial blocks:
| Block | Description |
|---|---|
| Invoice Summary | Displays invoice number, date, amount, and fiscal sequence (requires invoice context) |
| Payment Summary | Shows payment method, amount, date paid, and reference for a specific payment (requires payment context) |
| Balance Due | Shows total price, amount paid, and outstanding balance, with a "Pay Now" button linking to the customer's payment page. When you compose an email on an order, the button can also suggest a participant and an amount (see Composing an email) |
| Participant Overview | A card for one participant: the order code, their name, their total price, the payments registered to them, and a button to their overview page. It shows no balance and no pay link. Sent to a participant, the card is theirs; when several participants share the recipient's address, each gets a card; a recipient who is not a participant gets nothing. CC and BCC addresses are copied on every recipient's email, so they get each of these cards, with its button to that participant's overview page. When you compose an email on an order, you can pick the participant instead (see Composing an email). |
Link blocks:
| Block | Description |
|---|---|
| Link to Overview | A button linking to the customer's order overview page |
| Link to Payments | A button linking to the customer's payment page. When you compose an email on an order, the block can also suggest a participant and an amount (see Composing an email) |
| Link to Participants | A button linking to the participant information page |
Special blocks:
| Block | Description |
|---|---|
| Custom Message | A placeholder that the operator fills in at manual delivery time. For automatic deliveries (event or schedule triggers), this block renders empty. Use it when you want to add a personal note to an otherwise templated email. |
Reusable Content Blocks
You can create reusable content blocks under Actions > Content Blocks. Each block has a name and a rich text body. Once created, a content block can be inserted into any action's email body using the editor toolbar. When the email renders, Itsy resolves the block's current content -- so updating a content block automatically updates every action that uses it.
This is useful for shared content like terms and conditions, contact details, or standard footer text that you want to maintain in one place. See the Content Blocks page for full details on creating and managing them.
Placeholder System
The placeholder system lets you personalize emails with real order, client, and payment data. There are two ways to insert dynamic content:
- Template variables -- Inline placeholders like
{{orderCode}}that you type directly into the subject or body. They resolve to plain text values at delivery time. - Information blocks -- Structured blocks (Order Information, Balance Due, Flight Bookings, etc.) that you insert from the editor toolbar. They render as formatted sections with labels, values, and links.
When editing an action, expand the Available inline placeholders panel below the editor to see every variable and its description. Each variable shows what it resolves to and, where applicable, which context it requires (such as invoice or payment context). See Editing an Action for details on the Content tab.
Template Variables
You can use inline template variables in both the subject line and body. These are replaced with real values when the action is delivered.
Order variables:
| Variable | Replaced With |
|---|---|
{{orderCode}} | The order reference code |
{{orderTotal}} | The order total price |
{{orderBalance}} | The outstanding balance on the order |
{{orderPaid}} | The amount paid on the order so far |
{{orderDepartureDate}} | The order start date (departure) |
{{orderBookingDate}} | The date the order was created |
{{tripName}} | The name of the trip the order is on, or the display name set on the order when one overrides it |
{{group}} | The order group name (replaced only when the order belongs to a group) |
Recipient variables:
These change with each copy: each recipient gets their own email, filled in with their own details.
| Variable | Replaced With |
|---|---|
{{recipientName}} | The full name of whoever receives this copy |
{{recipientFirstName}} | The first name of whoever receives this copy. Use it for greetings when an action sends to participants. |
{{recipientEmail}} | The address this copy is sent to |
The workspace admin, a custom email and any address with no name on record have no name, so {{recipientName}} and {{recipientFirstName}} are empty on their copies. A greeting such as Hello {{recipientFirstName}}, reads Hello , there, so keep name greetings to actions that send only to people on the order.
Client variables:
These show the order's client in every copy, including copies sent to participants.
| Variable | Replaced With |
|---|---|
{{clientName}} | The customer's full name, or the company name for a corporate customer |
{{clientFirstName}} | The customer's first name |
{{clientLastName}} | The customer's last name |
{{clientEmail}} | The customer's email address |
{{clientPhone}} | The customer's phone number |
Workspace and sender variables:
| Variable | Replaced With |
|---|---|
{{workspace}} | The workspace name. In the subject line this is the plain name; in the body it uses the display name. |
{{workspaceEmail}} | The workspace contact email address |
{{senderName}} | The sender name configured on the action, falling back to the workspace name |
{{senderEmail}} | The sender email configured on the action, falling back to the workspace contact email |
Invoice variables (require invoice context):
| Variable | Replaced With |
|---|---|
{{invoiceNumber}} | The invoice number |
{{invoiceDate}} | The invoice creation date |
{{invoiceAmount}} | The invoice total amount |
{{invoiceTax}} | The total tax on the invoice |
{{invoiceFiscalSequence}} | The fiscal sequence string for the invoice |
{{invoiceCustomerReference}} | The customer reference (e.g. PO number) on the invoice |
Payment variables (require payment context):
| Variable | Replaced With |
|---|---|
{{paymentAmount}} | The payment amount |
{{paymentMethod}} | The payment method name, or the provider type if no method is set |
{{paymentDate}} | The date the payment was settled |
{{paymentMaskedCard}} | The masked card number, when the payment was made by card |
{{paymentReference}} | The best available reference: masked card number or external transaction ID |
In the email body, money values are displayed with the workspace currency prefix (e.g. "USD 1,500.00"). In the subject line, money values appear as raw numbers so you can format them inline.
Emails are rendered in the workspace's configured language (English or Icelandic).
Email Attachments
You can attach files to action emails:
| Attachment Type | Description |
|---|---|
| Booking Attachments | Documents attached to individual bookings within the order |
| Order Overview PDF | The order overview document |
| Selected Invoice PDF | The PDF of a specific invoice |
| Payment Receipt PDF | The receipt PDF for a specific payment |
| External Attachments | Files uploaded to the order, bookings, or participants (capped at 20 MB total) |
Webhook Actions
Webhook actions let you notify external systems when events happen in your workspace. Instead of composing an email, Itsy sends a JSON payload to the URL you configure.
Payload Structure
Every webhook delivery includes a standard envelope with context about the event:
{
"version": "v1",
"event": "OrderConfirmed",
"eventId": 3,
"actionId": "...",
"actionCode": "...",
"actionName": "...",
"deliveryId": "...",
"workspaceId": "...",
"timestamp": "2026-04-26T12:00:00Z",
"context": {
"order": { ... }
}
}The context object varies by event type. For payment events it includes a payment object alongside the order. For invoice events it includes an invoice object. For Order Placed it includes the payment that placed the order, or null when the order was placed manually. For all other events, the context contains the full order snapshot.
Webhook payloads are designed to be self-contained -- the order snapshot includes bookings, participants, payments, invoices, client details, and external references so receivers do not need to call back to Itsy for additional data.
Security Headers
Every webhook request includes these headers automatically:
| Header | Description |
|---|---|
X-Itsy-Event | The event name (e.g., OrderConfirmed) |
X-Itsy-Delivery-Id | A unique identifier for this delivery attempt |
X-Itsy-Action-Code | The action's code |
X-Itsy-Timestamp | The Unix timestamp of the request |
X-Itsy-Signature | An HMAC-SHA256 signature of the request body, using the action's secret key. Format: sha256=<hex> |
To verify a webhook, compute the HMAC-SHA256 of the raw request body using your shared secret and compare it to the value in X-Itsy-Signature.
Retry Logic
When a webhook delivery fails (non-2xx HTTP status or network error), Itsy retries automatically with increasing delays:
| After failed attempt | Wait before next try |
|---|---|
| 1st | 1 minute |
| 2nd | 5 minutes |
| 3rd | 30 minutes |
| 4th | 2 hours |
| 5th and beyond | 6 hours |
Retries continue until the request succeeds or the maximum number of attempts is reached (configurable per action, default 5 total). With the default of 5, the initial send plus up to 4 retries are attempted. A background job checks for due retries every minute. Each attempt and its outcome are logged in the delivery's event history.
URL Requirements
Webhook URLs must use HTTPS and resolve to a public IP address. Itsy rejects URLs that point to private, loopback, or link-local addresses to prevent internal network access.
Electronic Invoice Actions
Electronic invoice actions transmit issued invoices as structured Peppol e-invoices through a transmission network. This action type is available only when your workspace has the e-invoicing feature enabled.
Unlike email and webhook actions, electronic invoice actions have no per-action configuration for content, sender, or recipient. The sender identity comes from your workspace and segment Peppol settings, and the recipient is routed by the client's Peppol participant ID frozen on the invoice. Clients without a participant ID are skipped and continue receiving invoices by email.
Bind an electronic invoice action to the Invoice Created event to transmit invoices automatically. Optionally also bind it to the Invoice Voided event -- when a voided invoice had already been transmitted, Itsy issues a credit note to reverse it on the recipient's end.
An electronic invoice action has no manual trigger. The order's top menu runs an action for the order as a whole, and there is no single invoice for it to transmit.
Managed Actions
Itsy provides pre-built managed actions for essential workspace operations. These handle common scenarios that every workspace needs:
- Order Overview -- Sends the order summary document to the customer
- Payment Receipt -- Sends after payment validation
- Payment Reminder -- Runs on a daily schedule, sending reminders to customers with outstanding balances
- Supplier Report -- Delivers supplier activity reports
- Gift Certificate Purchase -- Sends the certificate PDF to the purchaser after payment
- Trip Email -- Sends trip-related communications to participants
- Document Delivery -- A general-purpose action for sending order documents to the customer, with a composable body and multi-select document attachments
Managed actions differ from regular actions in important ways:
- You cannot delete them
- You cannot change the name, code, color, segments, recipients, or attachments
- You can customize the email subject, body, sender details, CC/BCC, and active status
You manage these under Settings > Managed Emails, or from Actions > Templates where you can customize the subject, body, and sender details for each one.
Action Templates
When creating a new action, you can start from a pre-built template instead of building from scratch:
| Template | Type | What It Sets Up |
|---|---|---|
| Blank | An empty email action with no pre-configured triggers | |
| Order Confirmation | Pre-configured with triggers for both internal and external order creation events | |
| Payment Confirmation | Pre-configured with a trigger for payment validation events | |
| Payment Reminder | Pre-configured with a daily schedule trigger and conditions for orders with outstanding balance that are not draft, not cancelled, and not already fully paid | |
| Webhook Blank | Webhook | An empty webhook action with no pre-configured triggers |
| E-Invoice | Electronic Invoice | An empty electronic invoice action. Only visible when your workspace has the e-invoicing feature enabled. Bind it to Invoice Created and optionally Invoice Voided to transmit invoices and credit notes over Peppol. |
Templates save time by setting up the trigger, conditions, and a starting configuration automatically. These creation templates differ from managed action templates -- see Templates for the pre-built actions you customize under Actions > Templates.
Segment Targeting
Actions can be restricted to specific customer segments. When you configure an action, you can select one or more segments from the Segments field on the action overview. If no segments are selected, the action applies to all customers. When segments are selected, the action only triggers for orders belonging to customers in those segments.
This lets you create targeted communications -- for example, a VIP welcome email that only goes to customers in your premium segment, or a local-language reminder for a specific market.
Common Tasks
Creating a New Email Action
- Navigate to the Actions section
- Click Add
- Choose a template (Blank, Order Confirmation, Payment Confirmation, or Payment Reminder)
- Enter the action name, code, and color
- Configure the email subject, sender name, and sender address
- Optionally restrict to specific segments
- Click Save -- this creates the action and opens it for editing
- On the Overview tab, tick the recipients and set CC/BCC and attachments
- On the Content tab, build the email body using the rich text editor and insert content blocks as needed
- On the Triggers tab, add triggers to control when the action fires
- Activate the action when ready
Creating a Webhook Action
- Navigate to the Actions section
- Click Add
- Choose the Webhook template
- Enter the action name, code, and color
- Set the Webhook URL (must be HTTPS)
- Configure a Signing Secret for payload signing (required for all webhook actions)
- Optionally restrict to specific segments
- Click Save -- this creates the action and opens it for editing
- On the Overview tab, set the HTTP Method (POST or PUT) and Max Attempts (default: 5)
- On the Triggers tab, add triggers to control when the action fires
- Activate the action when ready
Adding Triggers to an Action
- Open an action and go to the Triggers tab
- Enable the trigger type you want:
- For Manual, choose where the action can be sent from. An email action is set to Off, Available or Default at each entry point (Order header, Invoice list, Payment reminder, Payment receipt), and to Off or Available in the Order action menu; a webhook action can be shown in the Orders top menu. An electronic invoice action has no manual placement. See Manual Trigger Placements
- For Schedule, the action runs daily at 02:00
- For Event, select the specific event to listen for
- Optionally add conditions to filter when the trigger fires
- Save your changes
Setting Up Payment Reminders
- Create an action using the Payment Reminder template
- The template automatically sets up:
- A daily schedule trigger
- Conditions: balance is larger than 0, status is not Draft, status is not Cancelled, and the order is not already fully paid
- Customize the email subject and body
- Tick Client under recipients
- Activate the action
To send reminders at several intervals before a deadline (e.g. 56, 42, 28 and 20 days before the fully-paid date), use a multi-day date condition instead of creating one action per interval. See Sending a reminder on several days for a worked example.
Previewing an Email Action
You can preview how an action's email will look for a specific order in two ways:
- From the Content tab -- When editing an action's email body, click the Preview button below the editor. A panel opens where you select an order, and Itsy renders the email with that order's real data. The preview uses your unsaved edits, so you can experiment with content changes before saving.
- From an order's send panel -- When you send an email from an order (for example, a payment reminder or a receipt), the send panel shows a live preview with that order's data next to the email you are editing.
Both previews show the resolved subject line, sender and recipient addresses, and the full email body with all template variables and content blocks filled in. Information blocks render when their required data and context are available — for example, the Flight Bookings block only appears when the order has Amadeus tickets. This lets you verify the message before it goes out.
Running a Manual Action
- Open an order
- For an email action, open the send panel from the entry point it is placed at: Send documents at the top of the order, Send in an invoice's menu, Send payment reminder on the order overview, or Deliver in a payment's receipt menu. Pick the action in the Action list if the panel did not open with it, review the email, and click Send. An action placed in the Order action menu is listed by name in the menu at the top of the order, and picking it opens the send panel with that action selected.
- For a webhook action, click its entry in the order's top menu. It runs immediately.
Reviewing Delivery History
- To see deliveries for a specific action: open the action and go to the Deliveries tab
- To see all deliveries across your workspace: go to the Deliveries report under Actions
- Filter by action, status, or date range as needed
- Click on a delivery to see its full event log. For email deliveries this includes events such as submitted, delivered, and bounced (older deliveries may also include an opened event); for webhook deliveries it includes submitted, individual attempt results, retry-scheduled events, and the final outcome.
- For email deliveries, click the envelope icon on the row to view the Sent Copy -- the archived email exactly as the recipient received it
Customizing a Managed Action
- Go to Settings and find Managed Emails
- Select the managed action to customize (Order Overview, Payment Receipt, Payment Reminder, Supplier Report, Gift Certificate Purchase, Trip Email, or Document Delivery)
- Edit the email subject and body
- Update sender details and CC/BCC if needed
- Save your changes
How It Connects
- Orders -- Most action triggers are based on order events. Deliveries are logged on the order timeline and can be viewed per client.
- Groups -- Group message events can trigger notifications. The Group contact recipient sends to the group's contact person.
- Gift Certificates -- Gift certificate creation can trigger delivery emails.
- Clients -- Corporate clients can have contacts with specific notification preferences (invoices, payment receipts, order confirmations), and actions route emails to the appropriate contacts automatically.
- Segments -- Actions can be targeted to specific customer segments, ensuring the right audience receives each communication.
- Editing an Action -- Detailed guide to the Overview, Content, Triggers, and Deliveries tabs when configuring an action.
- Templates -- Customize the pre-built managed action templates for order overviews, payment receipts, reminders, and more.
- Content Blocks -- Create reusable pieces of email content that you can insert into any action and maintain in one place.
- Coverage -- The coverage matrix shows which actions are configured for each trigger event and segment combination, helping you spot gaps.
- Deliveries -- Track the status and history of every email and webhook sent by your actions.