Does AgentRow sync with Notion or Confluence automatically?
Not today. Add or update documents and re-index; the builder API lets you script that from your own sync job.
A wiki is the best source for an internal assistant and the worst thing to paste into a prompt. Export or fetch the pages, index them as a knowledge base, and let the agent retrieve the relevant chunks with citations; use an HTTP API tool for live lookups of a specific page when freshness matters.
An internal assistant that answers policy and process questions from Confluence with a citation to the page.
An onboarding helper that walks new hires through Notion runbooks step by step.
A support agent that combines the public help centre (knowledge base) with a live Notion page for current incident status.
The shape a tool takes in the AgentRow builder API. Credentials are stored on the tool's auth settings, not in its configuration, so they never reach a prompt. Placeholders in double braces are filled by the model from the input schema.
{
"name": "notion_get_page",
"type": "http_api",
"description": "Fetch a Notion page's properties by id. Use for pages that change often, such as an incident status page.",
"auth_type": "bearer_token",
"safety_level": "safe_read",
"is_readonly": true,
"config": {
"method": "GET",
"url": "https://api.notion.com/v1/pages/{{page_id}}",
"headers": { "Notion-Version": "2022-06-28" },
"allowed_domains": ["api.notion.com"]
},
"input_schema": {
"type": "object",
"properties": { "page_id": { "type": "string", "description": "The Notion page id" } },
"required": ["page_id"]
}
}Every retrieval appears in the run trace with the query, the candidate chunks and their scores, the chunks that made it into the prompt, what was trimmed for the token budget, and whether a source chunk has changed since. Live page lookups through the HTTP API tool are logged like any other call.
Not today. Add or update documents and re-index; the builder API lets you script that from your own sync job.
When citations are enabled in the finalize node, the answer references the retrieved chunks it used, and the run trace shows exactly which chunks were cited.
The retrieval log shows both candidates and their scores, so you can see which one won and fix the source. Deduplication and the minimum score help, but the durable fix is in the wiki.
Ground AI agents in your documents: knowledge bases with chunking, embeddings, hybrid keyword and vector retrieval, reranking, citations and full logs.
Tool types, what a tool defines, how results reach the model, tool selection with search_tools, and authenticated tools for signed-in users.
Compare AgentRow and LangFlow for AI agents: visual workflows, multi-agent orchestration, RAG, observability and what it takes to run in production.
Slack, HubSpot, Stripe, Shopify, GitHub, calendar, email, wikis, webhooks and any REST API.
Join the waitlist for early access. Tell us which systems you need to connect and we will point you at the right tool definitions.