Native Automation Agent
Native Automation generates automations and native integrations from a prompt, with a visual flowchart of every step.
In short
- What it is: an AI agent that builds Jestor Native Automations from a prompt, inside Agents.
- What you can do: generate automations and native integrations, connect accounts from the chat when a login is needed, and review a visual flowchart of every step.
- How to start: in the left sidebar, click Agents, then click the lightning icon in the composer and choose Native Automation in Select agent (it is the default). Select at least one table, then describe the automation you want to build.
- Keep in mind: at least one table must be selected before the agent can generate automations. This agent uses AI credits.
What is it
Native Automation is Jestor's in-product agent for building automations. You describe what should happen in a chat, and it creates the automation on the tables you selected, using Jestor's library of 400+ Native Automations and integrations.
It gives you the same features for building automations that are also available through the MCP, without leaving Jestor. In the chat, the agent appears as Jestor Native Automation.
After it creates an automation, you can still open that automation in the table and review or edit the When trigger and Do actions. See Automation and Native Automations.
When to use
Use Native Automation when you want to:
- Generate an automation or a native integration from a prompt, instead of building every step by hand
- See a visual flowchart of the trigger, conditions and actions
- Connect an external account (for example Slack, Microsoft Teams, Gmail or WhatsApp) from the chat, when the automation needs a login
- Get guidance when something is missing, such as a required detail or a possible loop
How to use
The main way to open Native Automation is from Agents. In the left sidebar, click Agents. In the composer, click the lightning icon and choose Native Automation in Select agent. Native Automation is the default. The list also includes AI App Builder, Block Composer, Custom Automation, Request Agent, Jestor Helper (Beta) and New agent.
You can also open it in these ways:
- From a table. In the top right of the table, open the ... menu, click Manage automations, then Create new automation. Keep the AI Automation Builder tab (the other tab is Manual).
- From Create. Click Create, open More tools, then New Automation. Native Automation is the default in Select agent.
- From the New tab. In Agents, open the New tab and pick the Native Automation card.
- Open Native Automation using one of the paths above.
- Select at least one table in the chat. The composer shows how many tables you have selected (for example, @ 2). The agent needs a table to generate automations.
- In the composer, describe the automation you want to build. On the full-page chat, the placeholder reads Describe the automation you want to build. In the table panel, the heading is What do you want to automate? and the placeholder reads Describe your automation and we'll compose it ...
- Send the prompt. The agent may ask a clarifying question or point out something that is missing before it creates the automation. It may also warn you about a possible loop and ask how you want to handle it.
- If an action needs a connection or login, use the button in the chat to connect the account (see Connections below).
- Review the visual flowchart of the steps (see Flowchart below). When the automation is created, the chat confirms it with a notice such as A new automation named '...' has been created. The agent may say it created and enabled the automation in the table, and ask Would you like to test it? The header has Open automation, which opens the automation.
Your conversations live in Agents, like other AI chats. See AI Chats.
Example prompts
- "When a deal in Sales Pipeline changes to Won, create a project in Projects with the same client and notify the account owner."
- "When a paid order is created, send a Slack message and notify the team."
Connections
If an automation needs an external account or login, the agent shows a button in the chat for each service, such as Connect Slack or Connect Microsoft Teams.
- Click Connect [service] and complete the login.
- While the login is in progress, the chat can show Waiting for login...
- After you finish, click I've connected so the agent can continue and add the actions that depend on that account.
Once the account is connected, the chat shows the service as connected. You can connect more than one service in the same conversation if the automation uses more than one integration.
Flowchart
As it works, the agent can generate a visual flowchart of the automation's steps. The diagram can show:
- The trigger and the actions that follow
- Conditions and branches (for example, a different path when an order is paid)
- Actions that run in parallel
- How two automations relate to each other
For example, a flowchart can show Record updated leading to Title is empty?, with Yes going to Set Title to Pending and No going to No action.
Jestor's builders can generate these diagrams, not only this agent. Use the flowchart to confirm the logic, then adjust the automation in the table if you need to.
Testing
Native Automation does not run the automation itself. Running it would use your tokens. Instead, the agent prepares a test and shows a test card in the chat. The card is titled Test of the automation followed by the automation name. The subtitle says how many test records will be created in the table (for example, 2 test records will be created in the table :) and lists the values for each test record. Click Run test when you are ready. While it runs, the card can show Running test.... After it finishes, the card shows Test executed, and the agent confirms the result, for example The test passed. Both the empty Title and the existing Title became Pending.
The test can create real records and run the automation, and it may also run other automations on the same table. Read the test card before you run it.
If a test does not pass, the agent explains what failed and can adjust the automation.
The same kind of testing flow is available in Custom Automation.
Click Run test. After it finishes, the card shows Test executed, and the agent confirms the result.
You run the testThe agent prepares the test and reads the result, but you are the one who runs it. That keeps your tokens under your control.
Keep in mind
Select a table firstNative Automation needs at least one table selected in the chat before it can generate automations.
- This agent uses AI credits. See AI Credits.
- The automations it creates are standard Jestor Native Automations. They are stored on the table and only run on events that happen after they are activated. You can review, edit, or turn them off in the Table Automations panel (+ Automation in the table's action bar).
- The agent can guide you when something is missing and can warn you when a design might loop. An action that updates records can trigger other automations, so review chains before you rely on them.
- If a step needs a connection, complete the login from the chat button, then click I've connected.
- The agent does not run tests for you. Use Run test on the test card, then wait for the agent to confirm the result.
Related pages
- Custom Automation: create and edit Python low-code functions and triggers from a prompt in Agents.
- Native AI Agents
- AI Chats: conversations live in Agents.
- Automation
- Native Automations
- MCP: create and edit the same Native Automations from Claude, ChatGPT / Codex, Cursor or VS Code.
- AI Credits
FAQ
1. Do I have to select a table?
Yes. At least one table must be selected in the chat before the agent can generate automations. Select the table (or tables) the automation should run on, then describe what you want.
2. Does this use AI credits?
Yes. Native Automation uses AI credits from your plan. See AI Credits.
3. What if the automation needs a connection, such as Slack, Microsoft Teams, Gmail or WhatsApp?
The agent shows a Connect [service] button in the chat. Complete the login, then click I've connected so it can add the actions that depend on that account.
4. Can I edit the automation after it is created?
Yes. Open the table, click + Automation in the top action bar, and open the automation in the Table Automations panel. You can change the When trigger and Do actions there, or turn the automation off without deleting it. In the chat, Open automation in the header also opens the automation.
5. How is this different from the AI App Builder or the Block Composer?
The AI App Builder and the Block Composer build apps, tables and pages. Native Automation generates automations and native integrations from a prompt. You can also build automations by hand in the table, or through the MCP.
6. How is this different from creating automations with the MCP?
Both use Jestor's Native Automation features. Native Automation is the in-product chat in Agents. The MCP lets you discover, create, edit, enable and disable automations from assistants such as Claude, ChatGPT / Codex, Cursor or VS Code.
7. Where do I find a past Native Automation chat?
Click Agents in the left sidebar and look in the conversation list, or use the search box. See AI Chats.
8. Can one automation trigger another?
Yes. If an action updates a record in a way that meets another automation's trigger, that second automation will run. The agent may warn you about possible loops. Review the flowchart and the automations in the table before you rely on a chain.
9. Does the agent run the automation when it tests it?
No. The agent prepares a test card in the chat, titled Test of the automation. You click Run test, then the agent confirms whether it worked. If a test does not pass, the agent explains what failed and can adjust the automation. The same testing flow is available in Custom Automation.
10. Do the automations this agent creates use anything besides AI credits?
Yes. The agent uses AI credits while it creates or edits the automation. When the automation later runs, it also consumes automation runs. See Rate Limits and Usage.
Updated about 6 hours ago
