Connect Affinity to Cal
When something happens in Affinity, Notis takes the next step in Cal. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Affinity to Cal
Check availability before a deal call
Check your Cal calendar availability when an Affinity deal needs a meeting, so you can suggest a time without exposing event details.
Verify calendar sync before deal scheduling
On a schedule, check whether Cal is syncing with Google Calendar so you can catch connection issues before relying on it for deal meetings.
Confirm a pending deal meeting
When a deal meeting is ready to finalize, send a webhook request that asks Notis to confirm its pending Cal booking by UID.
Cancel a deal meeting when plans change
Send a Notis webhook with the Cal booking UID when an Affinity deal conversation is no longer needed, and cancel the active booking.
Add a participant to a deal meeting
When a deal discussion needs another participant, use a webhook request to add them as an attendee to the existing Cal booking.
Schedule a phone call event for a deal
Use an explicit deal workflow request to register a phone call event in Cal with the existing event type, organization and team details.
Check calendar sync before the workday
Check Cal's Google Calendar synchronization status on a morning schedule before relying on it for deal meetings and other scheduling.
Check availability for an investor introduction
Before offering an investor introduction, check Cal free and busy availability through a Notis webhook tied to the Affinity relationship context.
Confirm an investor meeting after alignment
Confirm an eligible pending Cal booking when the investor meeting has been agreed and a Notis webhook supplies the booking UID.
Supported Triggers and Actions
Notis builds workflows that link Affinity to Cal. A trigger fires from one place; an action lands in another.
Affinity triggers
Cal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add member to team
Adds a new member to a team.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add attendee
Adds a new attendee to an existing booking.
Add organization attribute option
Adds a new choice to an organization's single- or multiple-choice attribute.
Delete oauth client webhook
Permanently deletes a webhook for an OAuth client, stopping its event notifications.
Cancel booking via uid
Cancels an active booking using its unique identifier.
Check calendar availability
Checks a calendar's free and busy times without revealing event details.
Check gcal synchronization status
Checks the connection and sync status of a user's calendar integration.
Check ics feed calendar endpoint
Checks whether a calendar feed is accessible and contains valid calendar data.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Affinity and Cal
Connect any two apps with Notis in the middle.
Affinity and Cal, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cal.