Connect Hubspot to Coda

When something happens in Hubspot, Notis takes the next step in Coda. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Hubspot to Coda

View example

Turn New HubSpot Contacts Into Coda Briefs

Create a Coda doc for each new HubSpot contact, with a concise summary and suggested next steps based on the available contact details.

View example

Prepare a Coda Onboarding Doc for New Contacts

Copy a Coda onboarding template when HubSpot creates a contact, so there is a fresh doc ready for the follow-up process you describe.

View example

Add a Contact Page to Your Coda Hub

Create a page in a Coda doc for each new HubSpot contact, with a compact record and follow-up notes based on available details.

View example

Create a Coda Handoff Doc When a Deal Changes Stage

Create a Coda doc after a HubSpot deal stage update, summarizing the available deal context and the handoff information your team requests.

View example

Copy a Coda Playbook for a Deal Stage Change

Copy an existing Coda playbook doc when a HubSpot deal changes stage, creating a fresh working doc for the stage process you specify.

View example

Add a Deal Update Page to Coda

Create a page in a designated Coda doc when a HubSpot deal changes stage, recording the update and relevant deal context available to Notis.

View example

Grant Coda Doc Access After a Deal Is Won

When a deal changes stage, add a permission to a specified Coda doc for the user or group you identify, if the trigger data and instruction identify them.

View example

Add Coda Access for a New Contact

When HubSpot creates a contact, add permission to a specified Coda doc for a recipient you identify in the automation instruction.

Supported Triggers and Actions

Notis builds workflows that link Hubspot to Coda. A trigger fires from one place; an action lands in another.

Hubspot triggers

Coda actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add a category for pack

Add a publishing category for a given pack.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add a maker for pack

Set a maker for a given pack. used to display makers for a pack in the corresponding packs page.

ActionInstant

Contact Created Trigger

TriggerInstant

Add a permission for pack

Create or modify user, workspace, or global permissions for a given pack.

ActionInstant

Deal Stage UpdatedTrigger

TriggerInstant

Add custom domain

Add a custom domain to a published doc.

ActionInstant

Add permission

Adds a new permission to the doc.

ActionInstant

Begin content export

Initiate an export of content for the given page.

ActionInstant

Content export status

Check the status of a page content export

ActionInstant

Copy Document

Creates a copy of an existing coda document. this action allows you to duplicate a document while optionally specifying a new title and location for the copied document.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.