Automation · in AI Studio

Automate the busywork on the boards you already use.

Set a rule right on the Leads, Deals or Tasks board, or draw a workflow on a canvas. Add an AI agent where judgment helps and a person where approval matters. Test it on a real record before it goes live.

Capabilities · 21

From a one-line rule to a full workflow.

Start on the board with a rule. When the process grows, open it in the visual builder.

  • 21capabilities
  • 45presets

Rules on your boards

8
  • Leads
  • Deals
  • Tasks
  1. Automation on every board.Open the rule builder straight from the Leads, Deals or Tasks board. Or manage every rule from one hub in AI Studio.
  2. Per stage or everywhere.Attach a rule to one pipeline stage, or to all stages at once.
  3. 18 triggers.Stage entered or left, record created, updated or deleted, a field changed, email received, task completed, a schedule, lead converted or merged, a duplicate found, deal won or lost, task status, assignment and overdue.
  4. 16 actions.Send a notification, an email or a message to the client’s messenger, create a task or activity, assign an owner, update a field, add or remove a tag, move the stage, launch a workflow, run an AI agent, call a webhook, or file the email.
  5. Conditions.Fire only when the record matches, using 10 operators on standard and custom fields.
  6. Delays.Run an action right away, or after a set number of minutes or hours.
  7. Round-robin.Spread new records across a pool of people, or always give them to one owner.
  8. Personal messages.Insert the record’s fields, custom fields included, into any message.
Show all 8Show fewer

Start fast, check before it runs

4
  • 45 presets
  • Test
  • Log
  1. 45 ready presets.Start from “Welcome email”, “Create task on stage enter”, “Webhook on stage change”, “AI process on completion” and more, grouped by category.
  2. Test on a real record.See what a rule would do to a recent real record before you save it.
  3. A log of every run.See each run’s status: completed, running, failed or cancelled.
  4. Safe when a module is off.A rule that needs a switched-off module pauses and says so: “Paused: Sales is off.”

Visual workflows

8
  • Canvas
  • Approval
  • Retry
  1. Draw the process.Drag steps onto a canvas, configure each one, and watch a run move node by node.
  2. Four ways to start.One of 42 CRM events across leads, deals, contacts, companies, tasks, activities and invoices; a webhook call from another system; a schedule; or by hand.
  3. 19 action steps.Send an email or a message, create a task, activity, record or invoice, update one record or many, convert a lead, change the stage, assign the owner, add a note or a task comment, tag, notify, call any HTTP endpoint, or launch another workflow.
  4. Logic.Branch with Condition and Switch, pause with Wait, loop with For Each, and set fields along the way.
  5. A person can sign off.Add an Approval step, and the workflow waits until someone approves.
  6. Built for real failures.Retry a step that fails, or let the workflow continue past it.
  7. Test, then publish.Dry-run a workflow without side effects, run it for real, then publish it. Every past run is kept with per-step results.
  8. From rule to workflow.Outgrew a simple rule? Open it in the builder as a workflow.
Show all 8Show fewer

Your own record types

1
  1. Stage rules on custom entities.AdminWhen a custom record changes stage, require fields or a linked record, send a notification, or call a webhook.
Rules on the board

Every new lead gets an owner, a hello and a callback.

Dana runs sales for a furniture maker. On the Leads board she adds a rule for any stage: when a lead is created, assign it round-robin between three reps. She tests it on yesterday’s lead and saves it. For the welcome message and the callback an hour later, she opens the rule in the builder and adds the steps: Send message, Wait 1 hour, Create task.

Workflows

A won deal becomes an invoice, after finance says yes.

When a deal is won, Maria’s workflow creates the invoice from the deal, then stops at an Approval step for the finance lead. Once approved, it emails the client a thank-you and creates the kickoff task for the delivery team. If the email step fails, it retries before anyone has to look.

Webhooks

Your other systems can start a workflow too.

Publish a workflow with a webhook trigger, and it gets its own unguessable URL. The order form on your website calls it. The workflow creates a lead, an AI Agent step reads the request and picks its type, and a Switch sends it to the right pipeline.

AI in this module

AI where judgment helps.

Put an agent into the process, with the same limits it has everywhere else.

  1. An AI step in a rule.Choose “AI processing” as a rule’s action, and one of your agents works on the record when the rule fires.
  2. An AI Agent node in a workflow.Put an agent step anywhere on the canvas: classify a request, summarize a thread, draft a reply.
  3. The same limits.An agent in a workflow keeps its own autonomy level and checks the same permissions as a person. Add an Approval step wherever you want a human to sign off.
  4. Agents on a clock.For time-based work, schedule an agent or let its Pulse check its tasks. See AI Studio
Connected

Connected to the rest of APROS.

  • Sales

    The “Automation” button sits on the Leads and Deals boards, and rules can fire on lead converted, merged, duplicate found, and deal won or lost.

    See Sales
  • Projects & tasks

    Rules fire on task completed, status changed, assigned or overdue, and create tasks and activities.

    See Projects & tasks
  • AI Studio

    Rules and workflows are tabs of AI Studio and come in the same AI module. Their AI steps use your Studio agents.

    See AI Studio
  • Developers

    Start workflows from any system with an inbound webhook, and call any URL with the Webhook action or the HTTP request node.

    See Developers
FAQ

Automation questions.

Is automation part of every plan?

Automation rules and workflows live in AI Studio and come in the same AI module. On the launch price list, AI agents are named in the Business plan. Ask us about the others.

Do we need a developer?

No. Start from one of 45 presets, or build a rule from triggers, conditions and actions. Developers get an HTTP request step and webhooks when they need them.

Can we try a rule without touching real data?

Yes. A rule previews what it would do to a recent real record before you save it. A workflow has a test run with no side effects.

What happens if we switch a module off?

Rules that need it pause and say so, for example “Paused: Sales is off.”

Can a person approve a step?

Yes. Put an Approval step in a workflow, and it waits until someone approves.

Take the busywork off your team. Join the waitlist, or book a demo and we’ll automate one of your real processes with you.