+
Connect Outlook to Supabase
Automate Outlook and Supabase with AI
Supabase auth and database alerts forwarded to Outlook often sit unread in a shared inbox. Your Operator agent on OpenClaw ties both so a Supabase alert becomes a prioritized Outlook summary with suggested checks, and signup mail can trigger a lookup in Supabase for the matching user row. Hand it an email address and it shows Outlook history next to Supabase auth logs you are allowed to see.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Outlook and Supabase
What your agent does in Outlook
Accept calendar event invite
Accepts or tentatively accepts a calendar meeting invite on behalf of a user. Use this action when a user has received a meeting invitation and wants to indicate their attendance status (either confirmed or tentative). The organizer will...
Add event attachment
Adds an attachment to a specific Outlook calendar event. Use when you need to attach a file or nested item to an existing event.
Add mail attachment
Tool to add an attachment to an email message. Use when you have a message ID and need to attach a small (<3 MB) file or reference.
Batch move messages
Batch-move up to 20 Outlook messages to a destination folder in a single Microsoft Graph $batch call. Use when moving multiple messages to avoid per-message move API calls.
Batch update messages
Batch-update up to 20 Outlook messages per call using Microsoft Graph JSON batching. Use when marking multiple messages read/unread or updating other properties to avoid per-message PATCH calls.
Create Calendar Event
Creates a new Outlook calendar event, ensuring `start_datetime` is chronologically before `end_datetime`.
What your agent does in Supabase
Create project api key
Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates.
Delete an API key from the project
Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
Delete third party auth config
Removes a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method.
Get a third-party integration
Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref`.
List third-party auth integrations for project
Lists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.
Update an API key for the project
Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string.
How it works
Tell the agent what you want to happen between Outlook and Supabase, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Outlook, works out what to do, and runs the matching action in Supabase without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Outlook and Supabase
- How do I connect Outlook and Supabase to Operator?
- You authorize Outlook and Supabase once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Outlook and Supabase?
- Tell it the job and it moves between Outlook and Supabase as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
- Can my agent keep Outlook and Supabase in sync?
- Yes. It can watch Outlook and act in Supabase, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Outlook and Supabase integrations
Put your agent on Outlook and Supabase
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free