Automation Reference

Complete reference for automation triggers, actions, conditions, and templates

Complete reference for building automations in Alguna. This page documents every trigger, the data each one carries, every action and its parameters, the step types, the template syntax, and the condition expression language.

Automations are built in the dashboard, in the visual automation builder. There is no public automations API: the values on this page are the identifiers the builder and the engine use, and knowing them helps you read execution logs, write conditions, and reference data between steps.

---

Anatomy of an Automation

An automation is a named container. Each automation holds one or more versions, and each version holds:

• exactly one trigger — what starts a run
• a set of steps — what the run does
• the paths between steps, each optionally guarded by a condition

Only one version is active at a time. Editing an active automation mints a new draft version rather than mutating the running one.

Object	States
Automation	draft, active, archived
Automation version	draft, active, inactive

---

Trigger Types

Every trigger is one of two types.

Type	Description
event	Runs when a platform event of a chosen event type occurs
schedule	Runs on a calendar or interval schedule

Both types accept an optional condition and an execution policy. See Trigger filtering below.

---

Event Trigger Types

There are twelve event trigger types.

Event type	Name	Category	Fires when
payment_failed	Payment Failed	payments	A payment attempt fails
card_expiring	Card Expiring	payments	A customer’s stored card enters its expiry month
invoice_status_updated	Invoice Status Updated	invoicing	An invoice status changes
prepaid_usage_update	Prepaid Usage Update	usage_metering	Prepaid usage is updated
credits_depleted	Credits Depleted	usage_metering	A customer’s credits balance is fully depleted
subscription_sent_for_signature	Subscription Sent for Signature	quotes	A subscription is sent for signature
quote_signed	Quote Signed	quotes	Every signer has signed a quote and its signature session completes
subscription_status_updated	Subscription Status Updated	subscriptions	A subscription status changes
subscription_renewal_window_entered	Subscription Renewal Window Entered	subscriptions	A subscription’s contract end date falls within the renewal window
flow_session_completed	Flow Session Completed	subscriptions	A hosted flow session is completed
salesforce_opportunity_changed	Salesforce Opportunity Changed	crm	A Salesforce opportunity is created or changed
hubspot_deal_changed	HubSpot Deal Changed	crm	A HubSpot deal is created or changed

These are not the same as webhook events. Webhook subscriptions use a separate, larger catalogue of events (invoice.paid, subscription.activated, and so on) and cannot be used as automation triggers. Automation triggers use the snake_case identifiers above.

Event payloads

The fields below are the trigger’s event data. Reference them from a step as {{trigger.inputs.<field>}}, and from a trigger condition by their bare field name.

payment_failed

Field	Type	Always present	Description
paymentId	string	Yes	The ID of the failed payment
accountId	string	Yes	The ID of the customer associated with the failed payment
invoiceId	string	No	The ID of the invoice if the payment was for an invoice
paymentMethodId	string	No	The ID of the payment method used for the failed payment
amount	decimal	Yes	The amount of the failed payment
currency	string	Yes	The currency code of the payment (3-letter ISO code)
failureReason	string	Yes	The reason why the payment failed

card_expiring

Field	Type	Always present	Description
accountId	string	Yes	The ID of the customer the expiring card belongs to
paymentMethodId	string	Yes	The ID of the expiring card payment method
cardBrand	string	No	The brand of the expiring card (e.g. visa)
cardLastFour	string	No	The last four digits of the expiring card
cardExpiryMonth	integer	Yes	The month (1-12) the card expires
cardExpiryYear	integer	Yes	The year the card expires
isDefault	boolean	No	Whether the expiring card is the account’s default payment method

invoice_status_updated

Field	Type	Always present	Description
invoiceId	string	Yes	The ID of the invoice whose status was updated
accountId	string	Yes	The ID of the customer associated with the invoice
status	string	Yes	The new status of the invoice
externalReference	string	No	Optional external reference associated with the invoice

status is one of: draft, upcoming, pending_approval, scheduled, processing, issued, void, paid, canceled, overdue.

prepaid_usage_update

Field	Type	Always present	Description
priceId	string	Yes	The ID of the prepaid price
productId	string	Yes	The ID of the product associated with the prepaid usage
productName	string	No	The name of the prepaid product
subscriptionVersionId	string	Yes	The ID of the subscription version
accountId	string	Yes	The ID of the customer with prepaid usage
maxUsageBeforeOverages	integer	Yes	The maximum prepaid usage before overages apply
currentUsage	number	Yes	The current usage amount
usagePercentage	number	Yes	The percentage of prepaid usage consumed, as a fraction (0.8 is 80%)

credits_depleted

Field	Type	Always present	Description
customerId	string	Yes	The ID of the customer whose credits were depleted
creditType	string	Yes	The type of credits that were depleted (monetary or units)

subscription_sent_for_signature

Field	Type	Always present	Description
customerId	string	Yes	The ID of the customer
subscriptionId	string	Yes	The ID of the subscription
recipients	string[]	Yes	List of recipient email addresses
isReminder	boolean	Yes	Whether this is a reminder email
recipientType	string	Yes	The type of recipient: customer or internal

quote_signed

Field	Type	Always present	Description
quoteID	string	Yes	The ID of the signed quote
subscriptionID	string	Yes	The ID of the subscription the signed quote belongs to
accountID	string	Yes	The ID of the customer the quote belongs to

subscription_status_updated

Field	Type	Always present	Description
subscriptionId	string	Yes	The ID of the subscription whose status was updated
status	string	Yes	The new status of the subscription

status is one of: draft, sent, accepted, active, canceled, paused, pending_approval, rejected, withdrawn, expired.

subscription_renewal_window_entered

Field	Type	Always present	Description
subscriptionID	string	Yes	The ID of the subscription entering its renewal window
accountID	string	Yes	The ID of the customer the subscription belongs to
termEnd	string	Yes	The subscription’s contract end date (RFC3339)
daysUntilRenewal	integer	Yes	The number of days remaining until the term ends, as of this run
renewalKey	string	Yes	Stable dedup key for this term, formatted as <subscriptionID>:<termEnd>
currency	string	No	The subscription’s currency, when known
currentACV	string	No	The subscription’s current annual contract value, as a decimal string, when resolvable

flow_session_completed

Field	Type	Always present	Description
flowSessionId	string	Yes	The ID of the completed flow session
hostedFlowId	string	No	The ID of the hosted flow (absent for standalone views)
accountId	string	No	The account ID associated with the session

salesforce_opportunity_changed

Field	Type	Always present	Description
provider	string	Yes	The CRM provider the change came from (e.g. salesforce)
integrationID	string	Yes	The ID of the CRM integration connection
recordID	string	Yes	The opportunity’s id in Salesforce
recordURL	string	No	A link to the opportunity in Salesforce, if available
stage	string	No	The opportunity’s current StageName
stageEntered	boolean	Yes	True when this change moved the record into its current stage. False on first sight of a record.
changedFields	object	Yes	Field-level before/after values for every field that changed. May be empty.

hubspot_deal_changed

Field	Type	Always present	Description
provider	string	Yes	The CRM provider the change came from (e.g. hubspot)
integrationID	string	Yes	The ID of the CRM integration connection
recordID	string	Yes	The deal’s id in HubSpot
recordURL	string	No	A link to the deal in HubSpot, if available
stage	string	No	The deal’s current dealstage
stageEntered	boolean	Yes	True when this change moved the record into its current stage. False on first sight of a record.
changedFields	object	Yes	Field-level before/after values for every field that changed. May be empty.

Each entry in changedFields is keyed by the CRM field name and holds a before/after pair, so a condition can read changedFields.Amount.after.

---

Trigger Filtering

A trigger has no separate filter language. Narrowing happens in two places.

Condition

An optional condition attached to the trigger. It is a set of expr expressions combined with and, or, or not, evaluated directly against the event payload’s top-level fields.

usagePercentage >= 0.8
status == "overdue"
stageEntered && stage == "Closed Won"

If the condition is not satisfied, no run starts.

Execution policy

Policy	Behavior
always	Run every time the trigger fires and its condition passes
once	Run only once per unique value of a chosen event field

With once, you also pick an event field key — a field from the event payload, either a top-level key (accountId) or a dot path into a nested object (changedFields.Amount.after). The first event carrying a given value runs the automation; later events carrying the same value are suppressed.

Suppression is scoped to the automation, not to the version, so editing an automation does not reset its history and re-fire values it has already handled. Some event types refine the slot further — prepaid_usage_update scopes suppression to the commitment period and the prepaid price, so a customer can be alerted again in the next period.

---

Schedule Triggers

A schedule trigger carries one of two shapes.

Calendar

The shape the builder writes. Each field is a list of { start, end, step } ranges; the schedule fires at every point matching all of them.

Field	Description
year	Years to run in
month	Months (1-12)
dayOfMonth	Days of the month (1-31)
dayOfWeek	Days of the week (1 = Monday … 7 = Sunday)
hour	Hours (0-23)
minute	Minutes (0-59)
second	Seconds (0-59)
comment	Free-text note describing the schedule

Interval

Field	Description
every	A duration — { duration, unit } — between runs
offset	Optional duration shifting the phase of the interval

Automations do not accept cron expressions. A schedule is either a calendar or an interval shape; there is no cron field anywhere in the trigger model.

Duration units are seconds, minutes, hours, days, weeks, months, quarters, years.

---

Step Types

Type	Description
action	Executes one action
condition	Splits the graph; each outgoing path carries its own condition
delay	Waits for a duration before continuing
for_each	Runs a sub-flow once per item of an array from a previous step’s output
do_until	Repeats a sub-flow until an exit condition is met

The automation builder currently offers action, condition, and delay steps. for_each and do_until are executed by the engine and appear in automations that use them, but are not yet offered as choices in the builder.

Delay steps

A delay carries a duration and a unit — seconds, minutes, hours, days, weeks, months, years in the builder.

Condition steps

A condition step has no “then” and “else” fields of its own. Instead it fans out into branches, and each outgoing path carries its own condition expression. A path with no condition is the fall-through.

for_each steps

Field	Description
Array source	The previous step output to iterate over
Wait mode	all (wait for every iteration) or first_to_complete
Max parallel	Optional cap on concurrent iterations

do_until steps

Field	Description
Iteration interval	Duration to wait between iterations
Exit condition	Condition evaluated before each iteration, optionally against the output of a data-source action
Max iterations	Optional safety cap

---

Actions

There are twenty-six actions. The action list is a closed set — you cannot register a custom action.

Parameter names below are exactly as the engine serializes them. Note that a few CRM parameters end in a capitalised ID (recordID, integrationID, planID); the rest use Id.

Notifications

send_email

Sends a generic, customizable email to a customer.

Parameter	Type	Required	Description
accountId	string	Yes	The ID of the customer to send the email to
from	string	Yes	The sender email address
subject	string	Yes	The email subject line
body	string	Yes	The email body content in markdown format
previewText	string	No	Optional preview text shown in email clients before opening
overrideEmails	string[]	No	Optional list of email addresses to send to instead of the account’s primary email
cc	string[]	No	Optional list of email addresses to carbon copy
bcc	string[]	No	Optional list of email addresses to blind carbon copy
cta	object	No	Optional CTA for the email: text and link, both required when present

send_slack_message

Sends a Slack message to a selected Slack channel.

Parameter	Type	Required	Description
integrationId	string	Yes	The Slack workspace connection to use
channelId	string	Yes	The Slack channel to send the message to
messageBody	string	Yes	The Slack message body in markdown format

The workspace and channel are picked from connected Slack integrations rather than templated. If no Slack workspace is connected, users who can manage integrations can connect Slack inline from the action form; others are directed to Settings → Integrations.

send_webhook

Sends an HTTP POST request with a JSON body to a specified URL.

Parameter	Type	Required	Description
url	string	Yes	The URL to send the webhook to
body	string	Yes	The JSON body to send (must be valid JSON)
headers	object	No	Optional custom HTTP headers to include in the request

headers is a flat map of string header names to string values.

send_billing_info_request

Requests billing information from a customer via email.

Parameter	Type	Required	Description
accountId	string	Yes	The ID of the customer to request billing information from
subscriptionId	string	No	Optional subscription ID to associate with the request
captureBusinessInformation	boolean	No	Whether to request business information (company name, tax ID etc)
capturePaymentMethods	boolean	No	Whether to request payment method information
overrideEmails	string[]	No	Optional list of email addresses to send to instead of the account’s primary email
cc	string[]	No	Optional list of email addresses to carbon copy
bcc	string[]	No	Optional list of email addresses to blind carbon copy

share_customer_portal_link

Shares a link to the customer portal via email.

Parameter	Type	Required	Description
accountId	string	Yes	The ID of the customer to share the customer portal link with
customCopy	object	No	Optional custom copy for the email — subject, body, ctaText. If not provided, the organization’s default email copy is used
overrideEmails	string[]	No	Optional list of email addresses to send to instead of the account’s primary email
cc	string[]	No	Optional list of email addresses to carbon copy
bcc	string[]	No	Optional list of email addresses to blind carbon copy

Payments

send_card_expiration_reminder

Emails the customer a reminder that their stored card is expiring, with a link to update it.

Parameter	Type	Required	Description
accountId	string	Yes	The ID of the customer the expiring card belongs to
paymentMethodId	string	Yes	The ID of the expiring card payment method (from the Card Expiring trigger)
overrideEmails	string[]	No	Optional list of email addresses to send to instead of the account’s billing contacts
cc	string[]	No	Optional list of email addresses to carbon copy
bcc	string[]	No	Optional list of email addresses to blind carbon copy

Invoicing

retry_invoice_payment

Retries payment for a failed invoice using the default payment method.

Parameter	Type	Required	Description
previousPaymentId	string	Yes	The ID of the previous failed payment attempt
invoiceId	string	Yes	The ID of the invoice to retry payment for

Outputs: invoiceId, paymentMethodId, paymentId, status, failureReason.

send_invoice_reminder

Sends a reminder email for an issued or overdue invoice.

Parameter	Type	Required	Description
invoiceId	string	Yes	The ID of the invoice to send a reminder for
overrideEmails	string[]	No	Optional list of email addresses to send to instead of the default recipients
cc	string[]	No	Optional list of email addresses to carbon copy
bcc	string[]	No	Optional list of email addresses to blind carbon copy

send_invoice_reminders_bulk

Sends reminders for a list of invoices based on a set of filters.

Parameter	Type	Required	Description
invoices	object[]	Yes	The list of invoices to send reminders for — normally the output of get_invoices
status	string	No	Optional status to filter by: issued or overdue
accountIds	string[]	No	Optional list of customer IDs to filter by
dueInDays	integer[]	No	Exclude any issued invoice that does not match the specified number(s) of days until it is due
overdueDays	integer[]	No	Exclude any overdue invoice that does not match the specified number(s) of days overdue
overrideEmails	string[]	No	Optional list of email addresses to send to instead of the default recipients
cc	string[]	No	Optional list of email addresses to carbon copy
bcc	string[]	No	Optional list of email addresses to blind carbon copy

Outputs: sentInvoices, failedInvoices, skippedInvoices.

Subscriptions

cancel_subscription

Cancels a customer’s active subscription.

Parameter	Type	Required	Description
subscriptionId	string	Yes	The ID of the subscription to cancel
sendEmail	boolean	No	Whether to send a cancellation confirmation email to the customer
effectiveEndDate	date-time	No	Optional date when the cancellation should take effect. If not provided, the subscription is cancelled at the end of the current billing period

Outputs: subscriptionId.

send_subscriptions_autorenewal_notification_bulk

Sends auto-renewal notifications for a list of subscriptions based on a set of filters.

Parameter	Type	Required	Description
subscriptions	object[]	Yes	The list of subscriptions to send auto-renewal notifications for — normally the output of get_subscriptions
daysUntilRenewal	integer[]	No	Exclude any subscription that does not match the specified number(s) of days until renewal
customerIds	string[]	No	Optional list of customer IDs to filter by

Outputs: sentSubscriptions, failedSubscriptions, skippedSubscriptions.

Quotes

send_subscription_signature_reminder

Sends a reminder email for a subscription that requires signature.

Parameter	Type	Required	Description
subscriptionId	string	Yes	The ID of the subscription to send a signature reminder for
overrideEmails	string[]	No	Optional list of email addresses to send to instead of the default recipients
cc	string[]	No	Optional list of email addresses to carbon copy
bcc	string[]	No	Optional list of email addresses to blind carbon copy

create_quote

Mints a new, renewal, or amendment quote for an account, optionally linking it to a CRM opportunity.

Parameter	Type	Required	Description
kind	string	Yes	What the quote changes about its subscription: new, renewal, or amendment. Defaults to new
accountId	string	Yes	The account the quote is created for
planID	string	No	The plan a new quote is seeded from
subscriptionId	string	No	The subscription a renewal quote renews
opportunityId	string	No	A CRM opportunity to link the quote to once created

Outputs: created, quoteId, subscriptionId, opportunityId, reason.

activate_quote

Marks a quote’s subscription signed offline, mirroring the dashboard’s manual offline-sign action.

Parameter	Type	Required	Description
quoteId	string	Yes	The quote whose subscription should be marked signed offline

Outputs: activated, quoteId, subscriptionId, reason.

CRM

These actions require a connected CRM integration.

get_crm_opportunity

Reads a CRM opportunity and the Alguna account and quotes it correlates to.

Parameter	Type	Required	Description
recordID	string	No	The opportunity’s id in the CRM. Provide this or quoteId, not both
integrationID	string	No	The ID of the CRM integration connection. Defaults to the organization’s connected CRM when omitted; only meaningful together with recordID
quoteId	string	No	The quote whose linked CRM opportunity should be read. Provide this or recordID, not both

Outputs: opportunityId, externalId, name, stage, amount, currency, closeDate, ownerName, url, accountId, externalAccountId, quoteId, linkedQuoteIds.

create_crm_record

Creates or updates the quote’s CRM record of the requested object type, or an account-anchored expansion Opportunity.

Parameter	Type	Required	Description
objectType	string	Yes	The CRM object type to write
quoteId	string	No	The quote the record projects, and the quote a created Opportunity is linked to
accountId	string	No	The account a quote-less Opportunity is created against (Opportunity only)
recordContext	string	No	Which mapping context to resolve the record’s fields from
stage	string	No	The pipeline stage a created Opportunity opens in. Opportunity only
name	string	No	Optional Opportunity name override (Opportunity only)

Outputs: created, updated, skipped, externalId, opportunityId, reason.

update_crm_record

Writes billing and quote facts onto the subscription’s linked CRM opportunity.

Parameter	Type	Required	Description
quoteId	string	Yes	The quote whose linked CRM opportunity should be updated

Outputs: updated, skipped, opportunityId, reason.

set_opportunity_stage

Moves the stage of the opportunity linked to a quote. Opt-in only — use it when no CRM workflow already moves the stage for you.

Parameter	Type	Required	Description
stage	string	Yes	The Opportunity stage to set
subscriptionId	string	No	The subscription whose linked CRM opportunity’s stage should be set
quoteId	string	No	The quote whose linked CRM opportunity’s stage should be set
recordID	string	No	The Opportunity’s id in the CRM
integrationID	string	No	The ID of the CRM integration connection. Defaults to the organization’s connected CRM when omitted; only meaningful together with recordID

Provide exactly one of subscriptionId, quoteId, or recordID to address the opportunity.

Outputs: updated, skipped, opportunityExternalId, reason.

create_quote_from_opportunity

Mints a draft quote for a CRM opportunity’s customer and links the two, importing the customer when the deal has none here yet.

Parameter	Type	Required	Description
recordID	string	Yes	The opportunity’s id in the CRM
integrationID	string	Yes	The ID of the CRM integration connection
planID	string	No	A plan to seed the quote from. Left empty, the quote starts blank

Outputs: created, quoteId, subscriptionId, opportunityId, accountId, reason.

void_open_quotes_for_opportunity

Withdraws every open quote linked to a CRM opportunity, cancelling their pending signature sessions.

Parameter	Type	Required	Description
recordID	string	No	The opportunity’s id in the CRM. Provide this or quoteId, not both
integrationID	string	No	The ID of the CRM integration connection. Defaults to the organization’s connected CRM when omitted; only meaningful together with recordID
quoteId	string	No	A quote linked to the opportunity whose other open quotes should be voided. Provide this or recordID, not both

Outputs: opportunityId, quotesVoided, quotesSkipped, reason.

cancel_renewal_for_lost_opportunity

Schedules a subscription to stop auto-renewing at its current contract end date when its renewal Opportunity is marked lost in the CRM.

Parameter	Type	Required	Description
recordID	string	No	The opportunity’s id in the CRM. Provide this or quoteId, not both
integrationID	string	No	The ID of the CRM integration connection. Defaults to the organization’s connected CRM when omitted; only meaningful together with recordID
quoteId	string	No	The renewal quote whose linked CRM opportunity was marked lost. Provide this or recordID, not both

Outputs: scheduled, subscriptionId, effectiveDate, reason.

Lookups and general

get_invoice

Retrieves details of a specific invoice.

Parameter	Type	Required	Description
invoiceId	string	Yes	The ID of the invoice to retrieve

Outputs: the invoice fields listed under Invoice shape.

get_invoices

Retrieves a list of invoices based on filter criteria.

Parameter	Type	Required	Description
accountIds	string[]	No	List of customer IDs to filter invoices by
accountIdsToExclude	string[]	No	List of customer IDs to exclude from the results
statuses	string[]	No	List of invoice statuses to filter by

Outputs: invoices — an array of the invoice shape.

get_subscription

Retrieves details of a specific subscription.

Parameter	Type	Required	Description
subscriptionId	string	Yes	The ID of the subscription to retrieve

Outputs: the subscription fields listed under Subscription shape.

get_subscriptions

Retrieves a list of subscriptions based on filter criteria.

Parameter	Type	Required	Description
accountIds	string[]	No	List of customer IDs to filter subscriptions by
accountIdsToExclude	string[]	No	List of customer IDs to exclude from the results
statuses	string[]	No	List of subscription statuses to filter by
contractPeriodTypes	string[]	No	List of contract period types to filter by: fixed or monthly_rolling
autoRenew	boolean	No	Filter by auto-renew setting

Outputs: subscriptions — an array of the subscription shape.

set_tags_on_entity

Sets tags on an invoice, subscription, or customer.

Parameter	Type	Required	Description
entityType	string	Yes	The type of entity to tag: product, customer, plan, subscription, metric, or invoice
entityId	string	Yes	The ID of the entity to tag
tagIds	string[]	Yes	The tags to apply to the entity (at least one)

Outputs: entityType, entityId, tagIds.

---

Object Shapes

The lookup and bulk actions pass around reduced invoice and subscription shapes. These are the fields available on step outputs.

Invoice shape

id, accountId, subscriptionId, currency, status, amount, amountPaid, amountDue, issueDate, dueDate, overdueDays, dueInDays, autoPay, paidDate, voidDate, tagIds.

Subscription shape

id, name, accountId, status, currency, contractPeriodType, contractDuration, contractStartDate, contractEndDate, activatedAt, endedAt, autoRenew, renewalPeriodType, renewalDuration, cancelationReason, daysUntilRenewal, signedByCustomer, customerName, acv, arr, mrr, tagIds.

---

Template Syntax

Action inputs and path conditions can reference values produced earlier in the run. A reference is a dotted path in double braces, and it always has at least three segments: the source, inputs or outputs, and the field.

{{trigger.inputs.invoiceId}}
{{trigger.inputs.changedFields.Amount.after}}
{{get_invoice_step.outputs.amountDue}}
{{get_invoices_step.outputs.invoices}}

Source	Meaning
trigger.inputs.<field>	A field from the triggering event’s payload
<stepId>.inputs.<field>	An input that was passed to an earlier step
<stepId>.outputs.<field>	A value produced by an earlier step

A value that is entirely one reference resolves to that value with its type preserved — an array stays an array, a number stays a number. A reference embedded inside a longer string is substituted into the string:

Invoice {{trigger.inputs.invoiceId}} is overdue

References also work inside nested objects and arrays, such as the cta object on send_email.

There is no filter pipeline. {{ amount | currency }}, {{ now }}, and {{ secrets.KEY }} are not supported — a reference is a path into the run’s data and nothing else. Secrets belong in the connected integration, not in an automation input.

---

Condition Syntax

Conditions use the expr expression language. A condition is a list of expressions plus a logical operator that joins them.

Operator	Meaning
and	Every expression must be true
or	At least one expression must be true
not	Every expression must be false

Trigger conditions are evaluated against the event payload, so fields are referenced by bare name. Path conditions are evaluated after template references are resolved, so they reference step data with {{...}} paths.

Comparison operators

Operator	Description	Example
==	Equal	status == "overdue"
!=	Not equal	status != "draft"
>	Greater than	amount > 100
>=	Greater or equal	usagePercentage >= 0.8
<	Less than	daysUntilRenewal < 30
<=	Less or equal	overdueDays <= 30
in	Member of a list	status in ["issued", "overdue"]
not in	Not a member of a list	status not in ["void", "canceled"]

The builder also offers is null / is not null for scalar fields, and contains, does not contain, is empty, is not empty for array fields.

Logical operators inside an expression

Operator	Description	Example
&&	AND	stageEntered && stage == "Closed Won"
||	OR	status == "paid" || status == "void"
!	NOT	!autoPay

Collections and null

len(linkedQuoteIds) > 0
any(invoices, .status == "overdue")
all(subscriptions, .autoRenew)
invoiceId != nil

An identifier that is absent from a sparse change payload resolves to nil rather than failing to compile, which is what makes changedFields.Amount.after safe to write against CRM change events that carry only the fields that changed. An expression that cannot be evaluated against the payload is treated as not satisfied.

---

Execution Outcome Reasons

Actions that may legitimately write nothing report a reason on their output instead of failing. Reading these in the execution log tells you why a run did less than you expected.

already_active, already_automated, no_linked_opportunity, no_crm_integration, already_created, already_signed, already_void, already_expired, already_rejected, subscription_active, not_a_renewal_opportunity, already_cancelled, cancellation_already_scheduled, already_renewed, expansion_already_open, no_active_subscription, ambiguous_subscription, no_opportunity_link, stage_already_set, stage_owned_inbound.

---

Failure Handling

Automations have no per-step retry or fallback configuration. Behavior on failure is fixed:

• Invalid inputs — a required parameter missing, or a template reference that cannot be resolved — fail the step permanently. There is no retry.
• Execution failures — a downstream service being briefly unavailable, for instance — are retried automatically by the workflow engine.
• Outcome reasons are not failures. An action that reports skipped with a reason has succeeded; the run continues.

To branch on an action’s result, read its outputs in a following condition step rather than reaching for an error handler.

---

Next Steps

Automation Overview

Getting started with automations.

Triggers

Learn about trigger types.

Actions

Explore available actions.

Conditions

Build conditional logic.