ingestia.ioingestia.io
AI Agents

Agents that work with your company's data

Create an agent from a ready template, choose what it can read and put it to work: it responds with the source of the number, runs on its own at the scheduled time and only acts after someone authorizes.

Architecture of an agent

The flow you build, piece by piece

From trigger to delivery: the agent reads the data you allowed, checks documents and other systems, asks for approval before acting and delivers the answer with its source. And Flows chain all of it with pipelines and notifications.

Agent tools

Flows sit underneath everything: they trigger the agent, run pipelines and send notifications, in sequence.

Click a piece to see what it does.

Trigger

What it does

It is what puts the agent to work: someone asks in the chat, the scheduled time arrives, an event happens (a load failed, a metric went off track) or a Flow calls the agent in the middle of a sequence.

Example

Every Monday at 8 a.m., the executive agent prepares the weekly summary without anyone opening the screen.

Read in the documentation
On all plans. Agents use your company's AI key (OpenAI, Anthropic or Google); credits pay only for data usage.

Agents that work with your company's data

  • Start from a ready template

    Commercial, finance, marketing, executive, pipelines monitor — or describe what you want and the agent is built for you to review.

  • Response with the source

    The agent queries only the data you allowed and responds with the number, the explanation and where it came from.

  • Runs on its own

    Schedule: the weekly summary every Monday at 8am, the load checks every night.

  • Asks for authorization before acting

    Reprocess a pipeline, send a report by e-mail or WhatsApp: the agent proposes, a person approves.

  • Company documents and memory

    Discount table, targets, policies: the agent consults and cites. And remembers what the company taught.

  • Agent team and external tools

    An agent can consult experts and use tools from other systems (MCP), each approved beforehand.

Flows

Visual automation that chains agents, pipelines and notifications

Build the sequence by connecting boxes, without coding: what triggers it, what runs, what the agent analyzes and who gets the notification.

  • Starts on its own

    On a schedule or on an event: a load finished, another failed, a metric went off track.

  • Runs pipelines

    One box refreshes the Gold layer before the agent looks at the numbers.

  • Calls agents

    Ask the right agent for the analysis, the summary or the comparison, in the middle of the sequence.

  • Picks the path

    Conditions split the path: notify only if the target was missed, ask for approval only if action is needed.

  • Notifies who needs it

    Email, WhatsApp or report — and every run is recorded, step by step.

The agent inside: team, data, documents and actions connected in a single diagram. Fictitious demo data. Fictitious demo data.
The agent proposes reprocessing only the step that failed; the decision is made by a person. Fictitious demo data.