Build an AgentOS workflow with AI

Turn a business rule into a saved workflow, inspect the real steps, and decide when it can run. This example keeps Airtable contact notes in sync with Notion without creating duplicate contacts.

Before you start

Connect Airtable and Notion in AgentOS Connections. Your Airtable connection must have access to the source base and table; your Notion connection must have access to the destination data source. Identify the source Email and Notes fields and the destination Email and Notes properties.

Use AgentOS Assistant, or an authorized B Square MCP connection in a compatible AI host. The examples below are prompts for the assistant, not a JSON workflow import format.

1. Describe a precise rule

Replace the bracketed names, then paste:

Build and save an AgentOS workflow draft named “Sync contact notes”.

Source: Airtable base [BASE NAME], table [TABLE NAME].
Destination: Notion data source [DATA SOURCE NAME].
Trigger: a source record update.

Read the changed record. Match its Email to the Notion Email property using an exact match after trimming whitespace and lowercasing both values. Do not match by a person's name. Treat a blank email as no match.

If the complete search finds exactly one matching Notion page, update only its Notes property with the source Notes value. Preserve the source Notes text without rewriting it. If the source Notes is blank, skip the write. If the trimmed Notes text equals “REVIEW”, ask for my approval before writing. Rejecting approval must stop that write.

If there are zero or multiple matches, or the result set is incomplete, skip the write and notify me in AgentOS. Do not create a page or change any other property.

Read the current workflow catalog, action contracts, connection status, and actual resource schemas first. Ask if any named resource is ambiguous. Show the saved revision, validation, trigger, connections, and external writes. Do not publish, enable, or run it yet.

The important details are the matching key, what to do with blanks, and what to do when there is no unique match. AI should not choose those business rules for you.

2. Review the saved workflow

Check the actual saved workflow, not just the assistant's plan:

• The source and destination are the intended base, table, and Notion data source.
• Only Notes can change. The flow does not create contacts or pages.
• Matching follows the rule above, including pagination and incomplete results.
• Approval happens before the exceptional write, and rejection has a separate stop path.
• Missing permissions or invalid fields are reported rather than silently dropped.

Ask for changes in the same conversation:

Update the same workflow draft. Change the approval keyword from “REVIEW” to “CHECK”. Preserve every other rule and connection. Validate it and show the new saved revision. Do not publish or run it.

3. Publish, test, and enable deliberately

Saving, publishing, enabling future triggers, and running a test are separate operations. A published workflow starts with automatic triggers paused.

After reviewing the accepted revision, use its real ID and revision:

Publish workflow [WORKFLOW ID], saved revision [REVISION], with the trigger and external writes I just reviewed. Keep future triggers paused.

Test with one record you are willing to change. A test run can write to the real connected apps.

Run the reviewed published version once using [TEST RECORD ID] and the required input schema. This test may update only the matching test page's Notes property. Show me the run ID and actual result. Do not enable future triggers.

Then, if the result is correct:

Enable future triggers for workflow [WORKFLOW ID], published revision [REVISION]. Keep the reviewed matching, approval, and write limits unchanged.

A second example: generate, review, then publish marketing media

AgentOS also exposes template-based poster and video steps, human review, and supported Instagram actions. Start with complete, approved template inputs. Do not assume a recurring workflow can invent narration or select photos unless the current catalog explicitly provides that preparation step.

Build a manual workflow draft named “Review listing campaign”.

Use my selected poster template [POSTER TEMPLATE ID] and video template [VIDEO TEMPLATE ID]. Accept separate, complete posterInputs and videoInputs matching those templates, plus my approved captions. Read the current template bodies and workflow node contracts before mapping them.

Generate the poster and video, wait for their delivered results, and present them for my approval. Only after approval, publish the poster and reel to my explicitly selected Instagram connection [CONNECTION NAME]. Use the stable image artifact reference and video delivery reference supported by the Instagram actions, not stored expiring download URLs. If generation fails or I reject the review, do not publish anything.

Show the real saved draft, validation, inputs, review step, and publishing effects. Do not publish, enable, render, or run this draft yet.

Instagram requires a working supported professional-account connection. A catalog entry does not prove that your account is currently authorized.

Check the outcome

Ask for the run's completed steps, skipped branches, review requests, and actual destination results. A valid graph or a published definition does not prove a successful Notion update or Instagram post. If a write has an uncertain outcome, inspect that run before retrying it.

Verification: The workflow catalog, human-input contract, media composition contracts, and authoring skill were checked on November 9, 2026. These recipes were not enabled or executed against live customer data during this review.