send_webhook.
Every input can be a literal value or a reference to earlier data in the run, inserted from the variable picker on the field. See Template syntax.
Notifications
send_email
Sends a generic, customizable email to a customer.
Use cases: payment failure notices, usage threshold alerts, ad-hoc customer communication.
send_slack_message
Sends a Slack message to a selected Slack channel.
Pick a connected Slack workspace first, then a channel from that workspace. Channel options include public and private channels the connected Slack app can access. Workspace and channel are selected, not templated; the message body supports references to run data.
If Slack is not connected yet, users who can manage integrations can connect it inline from the action form. Others see helper text directing them to Settings → Integrations.
Use cases: high-value deal alerts, failed payment alerts, onboarding kickoff notifications.
send_webhook
Sends an HTTP POST request with a JSON body to a specified URL.
The request is always a POST.
headers is a flat map of header name to value.
Use cases: syncing billing events into your own app, triggering an external workflow.
send_billing_info_request
Requests billing information from a customer via email.
Use cases: collecting a new payment method after a failure, chasing missing tax details.
share_customer_portal_link
Shares a link to the customer portal via email.Payments
send_card_expiration_reminder
Emails the customer a reminder that their stored card is expiring, with a link to update it.
Pair it with the
card_expiring trigger, which supplies both parameters.
Invoicing
retry_invoice_payment
Retries payment for a failed invoice using the default payment method.
Both parameters come straight from the
payment_failed trigger. The step outputs the new paymentId, its status and, on failure, a failureReason you can branch on.
send_invoice_reminder
Sends a reminder email for an issued or overdue invoice.send_invoice_reminders_bulk
Sends reminders for a list of invoices based on a set of filters. Normally preceded byget_invoices.
The step reports
sentInvoices, failedInvoices and skippedInvoices, so a following step can act on what actually went out.
Subscriptions
cancel_subscription
Cancels a customer’s active subscription.send_subscriptions_autorenewal_notification_bulk
Sends auto-renewal notifications for a list of subscriptions based on a set of filters. Normally preceded byget_subscriptions.
Quotes
send_subscription_signature_reminder
Sends a reminder email for a subscription that requires signature.create_quote
Mints a new, renewal, or amendment quote for an account, optionally linking it to a CRM opportunity.activate_quote
Marks a quote’s subscription signed offline, mirroring the dashboard’s manual offline-sign action.CRM
These actions need a connected CRM integration. Where a parameter names a CRM record directly it is spelledrecordID and integrationID, matching the CRM trigger payloads.
get_crm_opportunity
Reads a CRM opportunity and the Alguna account and quotes it correlates to. Useful as a lookup step before branching.create_crm_record
Creates or updates the quote’s CRM record of the requested object type, or an account-anchored expansion Opportunity.update_crm_record
Writes billing and quote facts onto the subscription’s linked CRM opportunity.set_opportunity_stage
Moves the stage of the opportunity linked to a quote. Opt in to this only when no CRM workflow of your own already moves the stage.
Provide exactly one of
subscriptionId, quoteId or recordID.
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.void_open_quotes_for_opportunity
Withdraws every open quote linked to a CRM opportunity, cancelling their pending signature sessions.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.Lookups and General
Lookup actions fetch data for later steps to branch on or act over. Their output is available as{{<stepId>.outputs.<field>}}.
get_invoice
Retrieves details of a specific invoice.get_invoices
Retrieves a list of invoices based on filter criteria.get_subscription
Retrieves details of a specific subscription.get_subscriptions
Retrieves a list of subscriptions based on filter criteria.set_tags_on_entity
Sets tags on an invoice, subscription, or customer.Workflow Control
Waiting and branching are step types rather than actions:
There is no “stop” action. A branch simply ends when it has no further steps.
When an Action Does Nothing
Several actions can legitimately write nothing — a quote is already signed, an opportunity has no link, a stage already matches. Rather than failing, these reportskipped or created: false along with a reason such as already_signed or no_linked_opportunity. The run continues, and the reason appears in the execution log. See Execution outcome reasons.
There is no per-action retry or fallback setting. Invalid inputs fail a step permanently; transient failures are retried by the workflow engine automatically.
Best Practices
Look Up Before You Act
Use a get action and a condition step to confirm state before sending or charging.
Prefer Bulk Actions
On scheduled runs, use the bulk reminder actions rather than one step per record.
Read the Outcome
Branch on an action’s outputs instead of assuming it did something.
Test Thoroughly
Test with real trigger data before activating.
Next Steps
Conditions
Add conditional logic to your automations.
Triggers
Configure what starts your automations.
Reference
Every parameter and output, in one place.