Connect ActiveMerge to Connecteam

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

View example

Turn ActiveMerge onboarding packets into Connecteam accounts

Use an ActiveMerge onboarding packet to prepare Connecteam user accounts from the staff details supplied with the webhook.

View example

Archive departing staff after ActiveMerge offboarding

Use an offboarding request to archive the Connecteam users whose unique IDs are supplied with the request.

View example

Prepare a secure Connecteam upload link for an ActiveMerge file

When an ActiveMerge workflow sends a file-upload request, generate a time-limited Connecteam upload URL for the next step.

View example

Check onboarding packet names against Connecteam users

Use staff names or identifiers included with an ActiveMerge packet request to retrieve Connecteam user data for a review.

View example

Find the right Connecteam scheduler for a staffing request

Use an ActiveMerge staffing request to retrieve the account's available schedulers and report them for follow-up.

View example

Review Connecteam jobs for an ActiveMerge shift request

Use a shift request that includes the relevant Connecteam instance ID to retrieve its job objects for review.

View example

Check Connecteam forms while preparing an ActiveMerge packet

Retrieve Connecteam form definitions when an ActiveMerge workflow requests a check of the available forms.

View example

Review Connecteam custom fields for an ActiveMerge document

Retrieve Connecteam custom fields when an ActiveMerge document request needs a review of available staff data fields.

View example

Add Connecteam account context to the weekly document review

On a recurring schedule, retrieve Connecteam account details to include in a weekly ActiveMerge document workflow review.

Supported Triggers and Actions

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

ActiveMerge triggers

Connecteam actions

Recurring trigger

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

TriggerScheduled

Archive Users

Archives users without deleting their records.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Users

Creates multiple user accounts.

ActionInstant

Generate Upload URL

Generates a secure, time-limited URL for uploading a file.

ActionInstant

Get Chat

Retrieves team chats and channels.

ActionInstant

Get Custom Field Categories

Retrieves custom field categories.

ActionInstant

Get Custom Fields

Retrieves the custom fields associated with an account.

ActionInstant

Get Forms

Retrieves form definitions.

ActionInstant

Get Jobs

Retrieve jobs associated with a scheduler or time clock instance.

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.