An agent finds a convincing paragraph in Notion and follows it. The paragraph describes a temporary exception from last quarter. Another agent sees an Airtable base with the right name and says it has checked the underlying records. It has only discovered the base.

Both failures treat a find as understanding what it authorizes or proves.

Connected knowledge is useful when an agent can tell a source from a decision, a decision from a reusable instruction, and an old answer from a current fact. That is the work behind a Notion integration, an Airtable integration, and reviewed agent memory.

Check what the connection actually retrieved#

A provider’s API does more than a connector exposes, so start with the operation you called and the object it returned.

The Airtable connection in the integration guide exposes bases and current-user information, which identify the account and destination without showing that the agent read or changed table rows.

Provider credentials add another limit: Airtable personal access tokens are limited by scopes and resources. Finding a base, having permission for a task, and having an executable operation for it are three separate checks.

In Notion, distinguish the page object from the content that supports the answer. Read the provider’s page retrieval reference and the actual response, and never infer complete document coverage from a successful lookup. Keep the page identifier and record what the agent inspected.

Give a decision enough context to survive a handoff#

Take a launch review. A Notion page records a temporary approval of a different support process for a pilot customer, with the customer, pilot period, approver, and the condition that ends the exception. A summary saying “the company uses this support process” loses the information that made the decision reasonable.

Use a decision note with these fields:

Decision: what was agreed
Scope: which customer, team, project, or situation it applies to
Source: page or record identifier and the relevant passage
Owner: who can clarify or revise it
Status: proposed, approved, superseded, or withdrawn
Review trigger: the event or date that should cause another check
Open questions: what this decision does not resolve

Decide which parts of the note become reusable instructions, and keep the source reference attached when moving the decision to another tool.

Preserve disagreement#

Suppose a later page describes a different process. The agent locates the conflict, compares scope and timing, and identifies who can resolve it. A more recent page does not override an earlier one everywhere, since it can describe a different team or an unapproved proposal.

Ask for the source behind each claim. Keep the earlier decision as history and change what future work relies on. Deleted history makes an earlier action hard to explain, and a withdrawn instruction still in use misleads.

The same applies to Airtable destinations. Similar base names can stand for a prototype and a production process, so keep the base identifier and never treat the name as identity.

Save a method separately from its changing inputs#

A reusable method says how to prepare a customer escalation brief: locate the account, inspect the conversation, identify the unresolved commitment, and ask for approval before sending a response. The latest customer status is an input and stays out of the method.

Use skills for reviewed methods and memory for information the team chose to keep. Review, correct, or forget information when its usefulness changes. People decide what is saved; the agent does not learn company policy from every conversation.

An instruction for the next task:

Reuse the approved escalation method. Refresh the customer’s current status and the relevant conversation. If the retained instruction conflicts with a current source, show the conflict before acting.

Publish one decision where later work can find it#

When creating a Notion page, resolve the intended parent, review the proposed content, and check whether an existing page already owns the decision. The create-page reference for the connection shows the inputs and permissions to inspect.

After creation, keep the resulting page identifier with the originating task, so a later agent follows that reference and skips the search for a similarly titled page.

Test with a withdrawn exception, two pages that disagree, a renamed base, and an identity that cannot access the expected material. A pass means the agent states what it knows, its source, and which part needs another decision.