Skip to main content

Creating Your First Automation

This article walks you through setting up your first automation in Stax.ai CX, start to finish. We'll use one simple example: an automation

Written by Andrew Flowers

Overview

This article walks you through setting up your first automation in Stax.ai CX, start to finish. We'll use one simple example: an automation that sends a templated email when your team reaches a specific task in a project. Once you've done this once, every other automation follows the same pattern — pick it, configure it, attach it.

If you haven't read it yet, start with [Automations Overview] for the big picture.

Prerequisites

Before you begin, make sure you have:

  • A project with at least one task (or a task where you want the automation to live).

  • An email template saved in your Library, if you're setting up an email automation.

  • The details you'll need for configuration — in this example, who should receive the email.

Step-by-step: set up an email automation

  1. Open your project and go to its task list.

  2. Click Add Task to create a new task for the automation, or select an existing task.

Tip: Give the task a clear name that says what the automation does, like "Send census request email." Future you (and your teammates) will thank you.

  1. Click Attach Automation on the task. The Configure Automation window opens on the Pick Automation step.

  2. Search for the email automation and select it. The window moves to the Configure step.

  3. Fill in the configuration fields: a. Recipient — choose who the email goes to. b. Email template — select the template the automation should send.

  4. Click Attach Automation. The window closes and the automation now shows on the task.

  5. When you're ready, click Run now on the task to run the automation. CX queues the task and shows a confirmation message.

Configuration fields explained

  • Recipient — the person the automation sends the email to. Pick the right contact so the message lands where it should.

  • Email template — the pre-written message from your Library. The automation sends this template, so review it first to confirm the content is current.

  • Conditions (some automations) — optional rules that control when the automation triggers. For example, if an automation launches a follow-up project when this one completes, conditions let you decide exactly when that should happen. Your first automation can skip these — add conditions once you're comfortable with the basics.

You're all set!

Your task now has a working automation. You can confirm it worked by checking the task — after a run, the task keeps an activity log showing what the automation did and when. If a run has a problem, you'll see a Retry option on the task.

Tips

Tip: Start with one automation on one project. Once it runs smoothly, roll the same setup into more projects.

Tip: If you want this automation in every future project of the same type, add it to your project template instead of rebuilding it each time. See [Save to Project File Automation] for a full example of adding an automation to a template.

Note: Automations only do what their configuration says. If something sends to the wrong place, check the configuration fields first — that's almost always where the fix is.

Related articles

  • Automations Overview

  • Save to Project File Automation

  • Common Automation Recipes

Did this answer your question?