Know which vendor commitments need attention before the review.
Collect service evidence, compare it with documented commitments, and prepare a review packet that clearly separates facts from assumptions.
How this composition works
This workflow turns a scattered weekly vendor check into a repeatable evidence packet. The agent retrieves current service records and prior decisions, calculates observed performance, and highlights gaps. Account owners decide how to interpret exceptions and what to communicate externally.
Load the vendor register
Read the current owners, review dates, and commitments from the approved register.
Collect supporting files
Find service reports and contractual reference documents in the approved folder.
Trace open correspondence
Collect relevant vendor updates without sending or changing messages.
Route the review
Post the packet to owners and flag missing evidence for follow-up.
Connected systems
These are the real product connectors composed for this example, each scoped to the credential permissions your workspace approves.
Airtable
Query and create Airtable tables, fields, and records.
Explore connectorGoogle Drive
Read, search, and manage files in Google Drive.
Explore connectorOutlook
Read Outlook mail and calendar via Microsoft Graph (read-only).
Explore connectorSlack
Read channels and messages, post messages, and upload files as your Slack bot.
Explore connectorOptional skills
Where relevant, skills add reusable method and verification. The connectors and agent instructions remain the primary building blocks.
Try asking
More examples for Operations
Build a governed workflow like vendor sla review.
Tell us what your team repeats today. We will map the systems, approval boundaries, and first governed run with you.