Connect Hubspot to Dynamics365

When something happens in Hubspot, Notis takes the next step in Dynamics365. 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 Dynamics365

View example

Add new HubSpot contacts to Dynamics 365

Create a Dynamics 365 contact when HubSpot reports a new contact, so your team can follow up from its CRM.

View example

Turn new HubSpot contacts into Dynamics leads

Create a Dynamics 365 lead when a new HubSpot contact arrives, giving your sales team a lead record to review.

View example

Create a Dynamics account from a new HubSpot contact

Create a Dynamics 365 account for a newly created HubSpot contact when your process treats each new contact as a new account.

View example

Open a Dynamics case for selected new HubSpot contacts

For a defined intake process, create a Dynamics 365 case when a new HubSpot contact event represents a support request.

View example

Create a Dynamics opportunity from a qualified HubSpot deal

Create a Dynamics 365 opportunity when a HubSpot deal moves into the stage your team uses for qualified opportunities.

View example

Create a Dynamics lead when a HubSpot deal reaches qualification

Create a Dynamics 365 lead from the deal details when a HubSpot deal reaches a stage your process treats as lead-ready.

View example

Create a Dynamics sales order when a HubSpot deal closes

Create a Dynamics 365 sales order when a HubSpot deal reaches your closed-won stage and includes the order details your process needs.

View example

Open a Dynamics case for a HubSpot deal escalation

Create a Dynamics 365 case when a HubSpot deal moves into a stage your team uses to flag an escalation that needs tracking.

View example

Create a Dynamics invoice from a closed-won HubSpot deal

Create a Dynamics 365 invoice when a HubSpot deal reaches your invoicing stage and the required invoice details are available.

Supported Triggers and Actions

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

Hubspot triggers

Dynamics365 actions

Recurring trigger

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

TriggerScheduled

Get all invoices action

ActionInstant

Webhook trigger

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

TriggerInstant

Create Account

Creates a new account entity record in dynamics crm using the web api.

ActionInstant

Contact Created Trigger

TriggerInstant

Create Case

Creates a new case (incident) entity record in dynamics crm using the web api.

ActionInstant

Deal Stage UpdatedTrigger

TriggerInstant

Create Contact

Creates a new contact entity record in dynamics crm using the web api.

ActionInstant

Create Invoice

Creates a new invoice entity record in dynamics crm using the web api.

ActionInstant

Create Lead

Creates a new lead entity record in dynamics crm using the web api.

ActionInstant

Create Opportunity

Creates a new opportunity entity record in dynamics crm using the web api.

ActionInstant

Create Sales Order

Creates a new sales order entity record in dynamics crm using the web api.

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.