RumataAI workflow step and connector controls
Choose an AI model, tools, output format, and payer, or configure a service connector’s operation and credentials.
Step-by-step guidance.
Before you start
- Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.
AI Agent instructions and tools
An AI step runs inside your automation. The assistant you chat with to build your app works separately.
| Control | What it does |
|---|---|
| System prompt | Describe what this step should accomplish, which rules it must follow, and when it should finish. |
| Model | Enter the model identifier to use. Use a model available through the configured provider. |
| Max turns | Limit how many reasoning/tool rounds this step can take. The default is 6. |
| Tools search / activity checkbox | Find and enable the activities the AI is allowed to call. Uncheck one to remove it from the tool set. |
| Selected tool configuration | Complete the selected activity’s settings. The AI receives the configured tool when the workflow runs. |
Final answer format
Choose a consistent format for the data passed to the next step so it can use the result reliably.
| Control | What it does |
|---|---|
| Text | Return a text answer. |
| JSON object | Return a structured object; this is the default mode. |
| JSON Schema | Require a structured answer that satisfies the schema you provide. |
| Schema editor | Enter a JSON object defining the expected fields and rules. Leave the field to validate and apply it to the graph draft; fix any error before saving. |
Who pays and advanced settings
Review the payer before publishing a workflow other people can call.
| Control | What it does |
|---|---|
| Caller funded / Owner funded | Choose whether the caller or workflow owner pays for this AI step. Caller funded is the default. |
| Keep caller funded / Enable owner funded | Cancel or accept the owner-funding choice in its confirmation dialog. The setting is still part of the graph draft until Save. |
| Advanced → Maximum run cost (USD) | Set a cost ceiling for this agent run. Leaving it blank removes this explicit ceiling. |
| Tool local URL override | For development, route tool calls to a specified service address. |
| OpenRouter API key / project secret toggle | Provide your own key directly or through a project secret, or leave it blank to use the platform configuration. |
Service connectors
Connectors provide named operations for external services. Add one from Add step, then choose an operation and complete the fields shown for it.
| Control | What it does |
|---|---|
| Connector / operation | Choose the service and task to perform. Changing the operation changes the available fields and the request it sends. |
| Required operation fields | Complete fields marked with an asterisk. Their descriptions identify the required service IDs, content, or other values. |
| Body field → ƒx | Calculate a request-body value from the current run with JSONata. |
| Path or query field → key icon | Use a project secret for a value placed in the address or query parameters. |
| Credential / API key → key icon | Choose a saved secret rather than embedding the credential in the graph. The helper text says which header or query parameter receives it. |
| Secret selector / Use a fixed value | Pick a secret by name, or return to a fixed value. Switching secret mode clears the prior field value. |