Help Center / Start and Launch Your First Workflow

Tutorial

Launch Your First Workflow

Launch your first useful Super Agent workflow with tools, channels, and a clear next step.

7 min read
On This PageWhat a Useful First Workflow Looks Like
  1. What a Useful First Workflow Looks Like
  2. 1. Start With Your Super Agent
  3. 2. Create the First Agent or Use the Super Agent Directly
  4. 3. Connect Only the Tools You Need
  5. 4. Run a Small Test
  6. 5. Make It Repeatable
  7. First Workflow Checklist

What a Useful First Workflow Looks Like

Your workspace is ready when your Super Agent understands the job, can use the right context or tools, and has completed a small workflow you would run again.

Super Agent first workflow screen with a starter prompt, connected tools, run test button, and trace review panel
Start from one narrow task in the Super Agent, run a low-risk test, and review the trace before you save or schedule the workflow.

Use this quickstart when you want the fastest path from a new account to a working first workflow. You can start in the web app, then add Slack or Telegram once the basic request works.

1. Start With Your Super Agent

Open your Super Agent and describe one real outcome. Include the goal, source material, expected format, and any approval rule before the agent sends messages, changes records, or uses customer data.

Starter prompttext
Summarize the newest support emails, draft a Slack update, and ask before posting anything externally.

If you are still learning what the command center does, read "Meet Your Super Agent Command Center" before expanding the workflow.

2. Create the First Agent or Use the Super Agent Directly

For a one-time first test, ask the Super Agent to do the work directly. For a role your team will reuse, ask it to create your first agent with a clear responsibility such as support triage, sales research, or weekly reporting.

Keep the first version narrow. A focused agent is easier to test, inspect, and improve than a broad assistant with too many jobs.

3. Connect Only the Tools You Need

Connect apps and tools only when the workflow needs them. Start with one integration, run a read-only check, then approve write actions after the trace, the step-by-step run log, shows the agent is using the right account and data.

For team communication, connect Slack when teammates should message the Super Agent from channels. Connect Telegram when you want quick personal check-ins from mobile. Use the integrations tutorial when the workflow depends on Gmail, Linear, Stripe, or another business app.

4. Run a Small Test

Ask for a low-risk result that proves the workflow. For example: summarize the newest support emails, draft a Slack update without posting it, or prepare a weekly report from one connected source.

  1. Run a read-only check

    Ask the Super Agent to find or summarize information before it sends, edits, or deletes anything.

  2. Review the trace

    Open the step-by-step run log and confirm the agent used the expected account, source, and tool.

  3. Rerun the same prompt

    After you update instructions, repeat the same task so you can compare the result clearly.

Good first workflow tests
WorkflowSafe first testReview point
Support triageSummarize new ticketsCheck source inbox and labels
Sales researchDraft an account briefConfirm sources and company names
Weekly reportingPrepare a private reportCheck metrics before sharing

Review the answer, any approval prompts, and the latest trace. If the agent missed context or used the wrong tool, update the instructions and rerun the same prompt.

5. Make It Repeatable

After the first test works, save the request as a reusable prompt or schedule it as a recurring job if the task should run daily, weekly, or monthly.

Keep a human approval step for external messages and sensitive changes until your team has reviewed several successful runs.

First Workflow Checklist

Your first workflow is ready when the Super Agent or first agent completes real work, the required integration or channel has been verified, and you know where to inspect the trace when something needs tuning.

  • The agent completed one real task with useful output.
  • The required integration or channel has been verified.
  • You know where to inspect the trace when something needs tuning.

Was this helpful?

Your feedback helps us rank and improve Help Center articles.