Connect Agility cms to Baselinker

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

View example

Review BaseLinker orders alongside Agility content

On a schedule, check recent BaseLinker orders and review Agility CMS content for product or offer references that may need follow-up.

View example

Update BaseLinker products from an Agility content request

Start from an HTTP request when an Agility CMS content change is ready for a catalog update, then update the corresponding BaseLinker product.

View example

Check BaseLinker storage connections for content operations

On a schedule, retrieve available BaseLinker storages and report whether the connected sources needed for your content operations are available.

View example

Create a BaseLinker order from an Agility campaign request

Start from a webhook request containing campaign order details, then create a BaseLinker order for a supplied customer and product information.

View example

Keep BaseLinker order statuses handy for launch operations

On a schedule, retrieve BaseLinker order statuses and report their ids and names so Agility CMS launch instructions can reference the current list.

View example

Register shipment tracking from an Agility fulfillment request

When a webhook request carries tracking and courier details for an order, register the manually created shipment in BaseLinker.

View example

Review pending BaseLinker receipts for sales follow-up

On a schedule, retrieve receipts waiting to be issued and report the pending items for a person to review.

View example

Issue a BaseLinker invoice from a ready request

Start from a webhook request with an existing order and numbering series, then issue its invoice in BaseLinker.

Supported Triggers and Actions

Notis builds workflows that link Agility cms to Baselinker. A trigger fires from one place; an action lands in another.

Agility cms triggers

Baselinker actions

Recurring trigger

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

TriggerScheduled

Get External Storages List

List connected external storages.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Inventory

Creates or updates a product catalog.

ActionInstant

Get Inventory Documents

Retrieve inventory documents.

ActionInstant

Add Inventory Category

Creates a category or updates the existing category with the same identifier.

ActionInstant

Get Inventory Document Series

Retrieve available inventory document series.

ActionInstant

Add Inventory Document

Creates a draft inventory document that requires confirmation before it is confirmed.

ActionInstant

Get Inventory Purchase Orders

Retrieve inventory purchase orders.

ActionInstant

Add Inventory Manufacturer

Adds a manufacturer or updates the existing one with the same identifier.

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.