Connect Agent mail to Dialmycalls

When something happens in Agent mail, Notis takes the next step in Dialmycalls. 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 Agent mail to Dialmycalls

View example

Save Email Senders as Dialmycalls Contacts

Turn useful incoming AgentMail senders into Dialmycalls contacts so their details are ready for future alerts.

View example

Organize Email Requests into Dialmycalls Groups

Use new AgentMail messages to create Dialmycalls contact groups when a clear grouping request arrives.

View example

Review Dialmycalls Contacts Mentioned in Email

When an email asks for a contact-list check, retrieve the Dialmycalls contact list for review and follow-up.

View example

Get Dialmycalls Group Inventory from Email

Retrieve Dialmycalls groups when an incoming AgentMail message asks for a group inventory or planning review.

View example

Review Dialmycalls Text Broadcasts from Email

Retrieve text broadcast history when an AgentMail message requests a review of recent outreach.

View example

Review Dialmycalls Call Broadcasts from Email

Retrieve call broadcast records when a new AgentMail email asks for a calling activity review.

View example

Check Dialmycalls Do Not Contact Entries from Email

Retrieve do not contact entries when an AgentMail request calls for a blocked-recipient review.

View example

Retrieve Dialmycalls Caller IDs on Request

Get the caller ID inventory in response to an AgentMail request to check available caller IDs.

View example

Retrieve Dialmycalls Recordings on Request

List available Dialmycalls recordings when an AgentMail message requests a recording inventory.

Supported Triggers and Actions

Notis builds workflows that link Agent mail to Dialmycalls. A trigger fires from one place; an action lands in another.

Agent mail triggers

Dialmycalls actions

Recurring trigger

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

TriggerScheduled

Add Access Account

Tool to add a new access (sub) account. use when you need to delegate dialing capabilities to another user after setting up your master account.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Contact

Tool to add a contact to your contact list. use when you need to store a new contact's phone (and optional name, email, or group) before sending messages.

ActionInstant

New Email Received

Trigger for new emails in an AgentMail inbox

TriggerPolling

Add Group

Tool to add a new contact group. use after deciding the group name to organize recipients into groups.

ActionInstant

Delete Access Account

Tool to delete an access (sub) account by id. use when removing a sub account after deprovisioning.

ActionInstant

Delete Caller ID

Tool to delete a caller id. use when you need to permanently remove an existing caller id no longer in use.

ActionInstant

Delete Contact

Tool to delete a contact by id. use when you need to permanently remove a contact from your list.

ActionInstant

Delete Group

Tool to delete a contact group by id. use when you need to remove an existing contact group after confirming its id.

ActionInstant

Delete Recording

Tool to delete a recording by id. use when you need to permanently remove a custom recording after confirming its recording id.

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.