> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ledgerup.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Tasks
> Automate actions triggered by events across your connected integrations.
export const AriMention = () => @Ari;
export const SlackMessage = ({children, name = "Bailey", initials = "B", color = "#611f69", avatar = "/images/bailey-avatar.png", app = false, time = "2:47 PM"}) =>
{avatar ? : initials}
{name}
{app ? APP : null}
{time}
{children}
;
## 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
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 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.
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:
Transactions from your bank account, emails from customers, and contract events like opt-outs & renewals.
Invoice status changes, failed payments, subscription updates, new charges, refunds, and dispute notifications.
Renewal dates approaching, contract start/end milestones, and billing schedule triggers.
Deal stage changes, new contacts created, company updates, and engagement activity.
Opportunity stage changes, closed-won deals, account updates, and order status changes.
Payment received, invoice created, expense logged, and account balance changes.
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_due`
**Action:** Ari sends a professional dunning reminder email to the customer's billing contact, then posts a summary in your #collections Slack channel.
create a task: when a Stripe invoice becomes overdue, send a payment reminder email and notify #collections
**Trigger:** A customer's payment fails
**Action:** Ari sends a professional payment reminder email to the customer's billing contact, then posts a summary in your #collections Slack channel.
create a task: when a Stripe invoice becomes overdue, send a payment reminder email and notify #collections
**Trigger:** Salesforce opportunity moves to `Closed Won`
**Action:** Ari looks up the account's billing details and drafts an invoice based on the opportunity amount, then posts it for your approval.
create a task: when a Salesforce deal closes, draft an invoice for the deal amount and send it to me for approval
**Trigger:** Contract renewal date is 30 days away
**Action:** Ari posts a summary of the contract terms, current billing status, and outstanding balance to your #ar-team channel so you can prepare.
create a task: 30 days before a contract renewal, post a summary of the contract and current billing status to #ar-team
**Trigger:** Stripe subscription payment fails
**Action:** Ari identifies the customer, checks their payment history, and notifies your team with recommended next steps.
create a task: when a subscription payment fails, look up the customer and notify #ar-team with their payment history
**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.
create a task: when a subscription payment fails, look up the customer and notify #ar-team with their payment history
***
## Creating a Task
You can create tasks by talking to Ari in Slack:
create a task: when \[event], \[action]
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:
| Mode | Behavior | Best for |
| --------------------- | ---------------------------------------------------------------- | ----------------------------------------------- |
| **Approval required** | Ari posts a plan in Slack and waits for you to click **Approve** | Actions that modify data or contact customers |
| **Auto-execute** | Ari runs the action immediately when the event fires | Read-only actions like notifications or lookups |
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.
create a task: when a payment fails, send a reminder email. If no payment is received after 7 days, send a follow-up. If still unpaid after 14 days, notify #collections with a full account summary.
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.
: initials}