Skip to main content

Quickstart

On this page you create an agent from a ready-made template, test it, and activate it.

Before you start​

  • Access to Imaginne and to Agent Studio, at ai.nnumbers.com.br/agent.
  • A role that lets you build in the space you will work in. See Spaces and access.
  • A service account configured in the organization — it is what runs AI steps. If there is none, Studio says so. See Service account.

Step by step​

1. Choose a ready-made template​

Under New agent, open the gallery. Each template shows what it does, its use case, how long it takes to configure, and what it requires — and only appears as ready to use when everything it needs is allowed in your space.

For your first, Summarize a text is the shortest path: it only requires the service account.

2. Adjust what is yours​

The template opens already assembled. What usually changes:

  • the AI task's objective — what you would ask a person to do;
  • the input fields — what the agent receives when triggered;
  • the result fields — what it returns.

3. Save​

Save stores the draft. A draft does not run in production — it exists for you to work in.

4. Test​

Test runs the agent for real, with data you provide. It is a real run: durable and visible in the timeline — not a simulation.

You can also test a single step in isolation, without assembling the whole flow. See Testing before publishing.

5. Activate​

Activate publishes a version and makes it active in development. From then on the agent can be triggered.

The published version is immutable: continuing to edit creates a new draft, and the active version stays exactly as it was tested.

6. Follow it​

Every trigger creates a run, with a step-by-step timeline, input, output, and the reason for any failure. See Following runs.

What happens next​

  • To put it in production, you have to promote the same version — which requires a publishing role and evidence that it ran successfully in development. See Promoting and rolling back.
  • To have it run on its own, add a trigger: a schedule, an HTTP address, or a call from another agent.

Common errors​

SymptomLikely causeWhat to do
The template appears as "needs configuration"Something it requires is not allowed in the spaceThe screen lists what is missing; see Allowed resources
"A service account is required"The organization has no active service accountSee Service account
Publishing is refusedThe definition has a structural problemThe message names the step; see Execution errors
The AI step fails with no clear explanationIt does not declare what it should returnSee AI task

Next steps​