Skip to main content

What are Ari Tasks?

Ari Tasks are event-driven automations that fire when something happens in your connected integrations. Instead of manually checking Stripe, HubSpot, or your inbox for changes, you define a trigger and Ari handles the rest. For example, you can set up a task that automatically sends a payment reminder whenever a Stripe invoice becomes overdue, or cancel a subscription when a customer is marked as churned in your CRM. We have built Ari to handle all of the nuance. If you only want it to execute on customers that are only in the US, just include that in the operating procedure.

How Tasks Work

An event occurs

Something happens in one of your connected integrations. A Stripe invoice goes past due, a HubSpot deal moves stages, a contract renewal date arrives, or an email comes in from a customer.

Ari evaluates the trigger

Ari checks whether the event matches any of your configured task triggers. You control the conditions, so only the events you care about fire a task.

Ari takes action

Depending on your configuration and the operating procedure outlined, Ari either executes the action automatically or presents an approval plan in Slack for you to review first.

Supported Event Sources

Ari can listen for events from any of your connected integrations:

LedgerUp

Transactions from your bank account, emails from customers, and contract events like opt-outs & renewals.

Stripe

Invoice status changes, failed payments, subscription updates, new charges, refunds, and dispute notifications.

Contracts

Renewal dates approaching, contract start/end milestones, and billing schedule triggers.

HubSpot

Deal stage changes, new contacts created, company updates, and engagement activity.

Salesforce

Opportunity stage changes, closed-won deals, account updates, and order status changes.

QuickBooks

Payment received, invoice created, expense logged, and account balance changes.

Email

Inbound emails from customers, replies to collection threads, and bounce notifications.

Example Tasks

Here are some common tasks teams set up with Ari:
Trigger: Stripe invoice status changes to past_dueAction: Ari sends a professional dunning reminder email to the customer’s billing contact, then posts a summary in your #collections Slack channel.
Trigger: A customer’s payment failsAction: Ari sends a professional payment reminder email to the customer’s billing contact, then posts a summary in your #collections Slack channel.
Trigger: Salesforce opportunity moves to Closed WonAction: Ari looks up the account’s billing details and drafts an invoice based on the opportunity amount, then posts it for your approval.
Trigger: Contract renewal date is 30 days awayAction: Ari posts a summary of the contract terms, current billing status, and outstanding balance to your #ar-team channel so you can prepare.
Trigger: Stripe subscription payment failsAction: Ari identifies the customer, checks their payment history, and notifies your team with recommended next steps.
Trigger: Customer requests for your W-9 in email.Action: Ari identifies the customer, verifies they are a valid customer, then posts an approval message in Slack to send the W-9 to the customer.

Creating a Task

You can create tasks by talking to Ari in Slack: Ari will confirm the trigger, the action, and whether it should auto-execute or require approval. You can always adjust these settings later.
For actions that modify data (sending emails, creating invoices, updating records), Ari defaults to requiring approval. You can change a task to auto-execute once you’re confident in the setup.

Auto-Execute vs. Approval

Every task can run in one of two modes:
Start with approval mode for new tasks. Once you’ve reviewed a few runs and are confident Ari is doing the right thing, you can switch to auto-execute.

Task Chaining

Tasks can trigger other tasks. For example, you can set up a sequence where a failed payment triggers a customer lookup, which then triggers a reminder email, which then sets a follow-up reminder for 7 days later.
Task chains will automatically execute. Make sure you review the full chain before enabling auto-execute on any step that contacts customers or modifies data.