Connect Agenty to Dynamics365

When something happens in Agenty, 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 Agenty to Dynamics365

View example

Turn researched prospects into Dynamics leads

Send a researched prospect to a Notis webhook and create a Dynamics lead with the supplied details and research context.

View example

Add researched companies to Dynamics accounts

Create a Dynamics account when Agenty sends company details and useful research context to a Notis webhook.

View example

Create support cases from researched issues

Send an issue and its supplied website context to a Notis webhook to open a Dynamics case for follow-up.

View example

Attach Agenty research to a Dynamics record

Create a Dynamics note containing supplied research and link it to a supported record when its reference is provided.

View example

Create a Dynamics task for a research follow-up

Turn an Agenty finding that needs action into a Dynamics task using a Notis webhook and the details provided.

View example

Create opportunities from supplied buying signals

Create a Dynamics opportunity when Agenty sends a relevant buying signal and its supporting details to a Notis webhook.

View example

Create Dynamics contacts from researched people

Create a Dynamics contact from person details supplied by Agenty through a Notis webhook.

View example

Review Dynamics records against current research

On a schedule, query a supported Dynamics collection and use returned records to guide a research review or next step.

View example

Review Dynamics accounts for research gaps

On a recurring schedule, query a bounded set of Dynamics accounts and identify which records need updated company research.

Supported Triggers and Actions

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

Agenty 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

View all invoices.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Annotation

Creates a text or attachment note, optionally linked to a supported record.

ActionInstant

Create Account

Create a new account record.

ActionInstant

Create Email Activity

Creates and stores a draft email activity without sending the email.

ActionInstant

Create Case

Create a new case.

ActionInstant

Create Product

Creates a catalog product and returns its selected representation.

ActionInstant

Create Contact

Create a new contact.

ActionInstant

Create Product Price List Item

Adds an existing product and unit to an existing price list.

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.