Skip to content
Controller AI Controller AI Controller AI Docs

Your first agent

A good first agent task is small, verifiable, and reversible: one agent, one attached capability, one safe test, nothing published. This page gives you a prompt to paste and tells you what a complete result looks like.

The prompt

Section titled “The prompt”

Use Controller AI to create a private agent named “Customer follow-up.” Give it one ready integration action for creating a CRM note. Explain whether that action should require approval before attaching it, then test it with a safe account and representative input. Do not publish or share the agent. Tell me exactly what ran and what still needs attention.

Adjust the name and the action to your stack — the shape is what matters: create, attach one thing, decide the approval policy, test safely, report.

What happens under the hood

Section titled “What happens under the hood”

The coding agent will:

  1. Create the agent draft — drafts are private and mutable; nothing is visible to your organization until you publish.
  2. Search the integration catalog for the action and check whether the app is already connected. If not, it sends you to the browser to connect — credentials never pass through the terminal.
  3. Decide (with you) whether the action needs per-call approval. New integration actions run without approval by default, so this decision is the important one: an action that creates a note is low-risk; one that emails a customer is not.
  4. Attach the action and run it once in a Test conversation against a safe target.
  5. Report the evidence.

What a complete result looks like

Section titled “What a complete result looks like”

Hold the report to this standard — each item is checkable:

  • Why an integration action was chosen over a workflow tool (one operation was enough).
  • Which action was attached, on which connected account, and the approval decision with its reasoning.
  • The safe test that ran and its observed external result — the note exists in the CRM, not just a green status.
  • Any unresolved connection, configuration, or permission issue.
  • Confirmation that testing used the mutable draft in Test mode, and the agent remains private and unpublished.

Where to go from here

Section titled “Where to go from here”