Skip to main content
Tell Addison what you want checked and how often. It helps you build a workflow to do the work. You don’t need to create an analysis or artifact first.

​
Choose your data

Choose a project with the data you want to review. Start with one area of your business, such as revenue, inventory, or operations.
Use a project whose catalog contains the relevant tables or views. Check when the data refreshes so you can schedule the workflow after new data is available.
Need to bring data in first? See Connect your data.

​
Describe the workflow

Open Workflows → New workflow → Create with Addison and describe what you want:
Every morning at 8 a.m. Pacific, review yesterday’s sales and gross margin against plan. Investigate the biggest variances by region and product, and summarize what the finance team should look into.
You can choose a weekly or monthly schedule, or ask for a particular output, such as a report or HTML page. Start with the task you need done; refine the comparisons, business definitions, and format as you review the result. Addison helps build the workflow and the playbook it runs. The playbook holds the instructions for the analysis; the workflow adds the schedule and delivery. You don’t need to create either one by hand.
The 'Create workflow' dialog: 'What workflow do you want to create?' with a prompt field (placeholder e.g. 'email the weekly revenue report every Monday at 9am') and Default/Medium effort controls.

Describing the workflow to Addison

Already have an analysis you want to repeat? Choose Create workflow from its report, HTML page, or other artifact.

​
Test it and confirm the schedule

Review the workflow Addison creates. Check that it uses the right project, schedule, and timezone. If it includes delivery, check the recipients too.
The workflow editor for 'Weekly Merchandising Review', showing a Schedule node ('Monday at 9:00 AM, Every Monday at 09:00 PT'), a Playbook node ('Merchandising Review' with its parameters), and a 'Send an email' node, wired top to bottom. The right sidebar shows Status 'Active', Project 'Operations', Created by 'Unknown', Last updated 'Sep 1, 2026', Next run 'Monday, Sep 7, 9:00 AM PDT', and a 'Run now' button.

A workflow ready to run, with its schedule and next run time

Run now starts a real run, including any delivery steps. It is not a preview. For an initial test, use only the recipients who should receive the test output. Open the result and check that it uses yesterday’s actuals and the matching plan. Does it highlight the variances your finance team would care about? Trace a surprising number back to its source, and use verification to review the available checks. If something needs to change, tell Addison:
Show sales net of returns, and separate margin changes caused by product mix from changes in product margins. Put the largest dollar variances first.
Update the playbook instructions for future runs, then test again. Editing one output alone doesn’t change what the workflow will do next time.
Saving a complete draft marks the workflow Active. Saving doesn’t start a run immediately, but an enabled schedule will run at its configured times. Review these settings before saving, and check Next run to confirm when the workflow will run.
Schedule the work after its source data refreshes, allowing time for analysis and delivery. Once you’re happy with the result and settings, the workflow can repeat the work on that schedule.

​
Next

Get verified insights

Investigate a question and check the evidence behind the answer.

Automate recurring work

Go deeper on reusable instructions, testing, and delivery.