Connect Agile CRM to DocRaptor

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

View example

Weekly Agile CRM Pipeline Review PDF

Turn current Agile CRM pipeline data into a concise PDF review of deals, next steps, and records that need attention.

View example

Monthly Agile CRM Campaign Workbook

Generate a monthly XLSX workbook from available Agile CRM campaign information for a structured performance review.

View example

Agile CRM Prospect Brief on Request

Start a webhook run with prospect context and create a concise PDF brief for an upcoming sales conversation.

View example

Agile CRM Support Escalation Pack

Use a webhook request with case details to prepare an async PDF pack summarizing the issue and its known context.

View example

Agile CRM Follow-up Priority List

Create a scheduled PDF list of CRM records that appear to need follow-up, based on available data and criteria in your instruction.

View example

Agile CRM Month-end Forecast Workbook

Generate an async XLSX forecast workbook from available Agile CRM sales data and the assumptions you provide.

View example

Agile CRM Customer Renewal Review

Create a renewal review PDF when a webhook request provides the customer context and renewal details available to you.

View example

Agile CRM Open Task Review

Create a scheduled PDF review of open Agile CRM tasks using the criteria and available task details in your instruction.

View example

Agile CRM Sales Handoff Brief

Use a webhook request with deal context to generate an async handoff brief for the next person involved in a sale.

Supported Triggers and Actions

Notis builds workflows that link Agile CRM to DocRaptor. A trigger fires from one place; an action lands in another.

Agile CRM triggers

DocRaptor actions

Recurring trigger

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

TriggerScheduled

Create Async Document

Creates a document asynchronously from HTML content.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Document

Creates a PDF or Excel document from HTML content or a URL and returns it immediately.

ActionInstant

Create Document from Referrer

Converts webpages into PDF or Excel documents.

ActionInstant

Create Hosted Async Document

Creates a hosted document asynchronously.

ActionInstant

Download Async Document

Downloads a completed asynchronous document.

ActionInstant

Get Async Document Status

Checks the progress of asynchronous document creation.

ActionInstant

List Documents (JSON)

Lists previously created documents with metadata in JSON format.

ActionInstant

List Documents (XML)

Lists previously created documents with metadata in XML format.

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.