Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.maadify.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What a parent agent does

Parent agents orchestrate workflows. They run on chat or triggers, call tools, and coordinate sub-agents to complete tasks.
Parent agent configuration showing tabs for sub-agents, rules, and triggers

​
Core building blocks

  • Sub-agents define the prompts and outputs used in your workflow.
  • Tool executions run connector tools with templated inputs.
  • Rules evaluate conditions and route to the next step.
  • Triggers start the workflow from schedules or webhooks.
  • Approvals and errors pause or stop execution based on outcomes.

​
Create a parent agent

1

Open the create form

Go to Agent Configurations and select Add Parent Agent.
2

Choose a Parent Agent Type

Parent Agent Type is the high-level category for your agent (for example, General Agent). It identifies what kind of parent agent you are building and is used to group agents of the same kind.
3

Choose an Action

Action is a sub-category of the selected Parent Agent Type. It narrows down the agent’s primary purpose within its category and helps further classify the parent agent. The available actions depend on the type you selected; if a type has no actions, this field is hidden.
4

Name the agent

Enter a Parent Agent Name that is unique and reflects the agent’s category and action. The Parent Agent Name Key is generated automatically from the name and used as the agent’s stable identifier.
5

Define purpose and scope

Add a clear Description of what the agent should accomplish.
6

Save and open configuration

Select Create Parent Agent. You can now add sub-agents, tools, and triggers.
Create Parent Agent form showing Parent Agent Type, Action, Parent Agent Name, Parent Agent Name Key, and Description fields
Think of Parent Agent Type as the category and Action as the sub-category. Together they classify the agent so it’s easier to find and reuse later.

​
Parent agent configurations

Use Parent agent configurations to control default behavior for the entire flow. You can open the form from Actions → Edit Parent Configuration in the flow view.
1

Open the configuration form

In flow view, select Actions → Edit Parent Configuration (or View Parent Configuration if you do not have edit permission).
2

Update defaults

Change the behavior you want to apply across the flow, then save.
Parent agent configuration showing tabs for sub-agents, rules, and triggers

​
What each configuration does

  • Active: turns the parent agent on or off.
  • Max conversation rounds: caps how many agent-to-agent turns can occur in a single run.
  • Default agent on continued conversation: chooses the first sub-agent when a conversation continues; if empty, standard routing rules are used.
  • Continue with last agent: keeps the last agent for a continued conversation when no default agent is set.
  • Default LLM model: fallback model when a sub-agent does not specify one.
  • Default temperature: fallback creativity level when a sub-agent does not specify one.
  • Memory expiration settings:
    • Thread TTL (hours): short-term memory for the current thread.
    • Agent TTL (days): medium-term memory across conversations for this agent.
    • Tenant TTL (days): long-term memory across the organization.
    • Clear thread on end: clears thread memory when the conversation ends.
Use defaults for consistency across sub-agents, then override at the sub-agent level only when you need different behavior.

​
Go deeper

Flow builder

Learn how nodes, edges, and rule order map to execution.

Sub-agents in flows

Add or edit sub-agents directly from the flow configuration.

Tool executions

Configure payloads, loops, and templated tool inputs.

Maadify Browser Agent

Configure browser tools that agents can use to navigate, act, and extract data.

Rules and routing

Define conditions, actions, and approvals that route workflows.

Triggers

Start workflows using schedules or webhooks.

Sub-agents

Build reusable sub-agents that plug into parent agents.

Prompt templates

Reuse prompts and variables across agents.