Connect ActiveTrail to Datagma

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

View example

Enrich ActiveTrail Leads Before Follow-Up

On a schedule, enrich a selected ActiveTrail contact list with Datagma person and company details to help prioritize follow-up.

View example

Find Work Emails for Campaign Responders

When an HTTP request starts the workflow with a person's name and company, ask Datagma to find a verified work email for follow-up.

View example

Research Companies Behind ActiveTrail Prospects

Periodically enrich selected ActiveTrail prospect records with Datagma company details to prepare more relevant outreach.

View example

Check Whether a Contact Changed Jobs

Use a webhook request with a contact email to ask Datagma whether that contact's employment has changed.

View example

Check Datagma Credits Before Lead Research

Run a scheduled Datagma credit balance check and review the remaining balance before planning enrichment work.

View example

Find Phone Numbers for Selected Campaign Contacts

Start from an HTTP request with an email or LinkedIn profile URL and ask Datagma to search for mobile phone numbers.

View example

Look Up Details Associated with a Contact's Phone

When a webhook sends a phone number, ask Datagma to return available associated details such as carrier or location.

View example

Find a Twitter Profile from a Campaign Contact Email

Use a webhook request with an email address to look for associated Twitter profile information in Datagma's database.

View example

Enrich a Contact's Twitter Username Before Research

Send a Twitter username in a webhook request and ask Datagma for associated professional and social profile details.

Supported Triggers and Actions

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

ActiveTrail triggers

Datagma actions

Recurring trigger

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

TriggerScheduled

Detect Job Change

Check whether a contact has changed jobs and verify their current employment.

ActionInstant

Webhook trigger

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

TriggerInstant

Enrich Person or Company

Enrich person or company data with contact, profile and business details.

ActionInstant

Find Work Email

Find a professionally verified work email address for a person.

ActionInstant

Get Credits

Retrieve the current credit balance.

ActionInstant

Get Twitter Profile By Email

Find the Twitter profile associated with an email address.

ActionInstant

Get Twitter Profile by Username

Retrieve contact and professional details associated with a Twitter username.

ActionInstant

Reverse Phone Lookup

Look up information associated with a phone number.

ActionInstant

Search Phone Numbers

Find mobile phone numbers associated with an email or LinkedIn profile.

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.