Connect Affinity to Convertapi

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

View example

Turn an Affinity pitch deck PDF into an editable DOCX

Start from an Affinity deal or contact, then convert its linked pitch deck PDF into an editable Word document.

View example

Create JPG page previews for an Affinity deal PDF

Use an Affinity deal as context to convert a linked PDF into individual JPG page previews.

View example

Check whether an Affinity attachment can be converted

Check ConvertAPI support for a supplied file and target format before proceeding with a conversion request.

View example

Convert a large Affinity document asynchronously

Run long or large file conversions asynchronously to avoid client timeouts, starting from supplied Affinity context.

View example

Retrieve a converted file for an Affinity workflow

Download a converted file from ConvertAPI using its FileId supplied with Affinity deal or contact context.

View example

Clean up temporary uploads after Affinity document work

On a recurring schedule, delete ConvertAPI uploaded files that are no longer needed for Affinity document workflows.

View example

Delete completed async jobs no longer needed

Run a scheduled cleanup for asynchronous conversion jobs confirmed as no longer required in Affinity workflows.

View example

Check ConvertAPI capacity before planned Affinity work

Check account balance and remaining seconds on a schedule before upcoming Affinity document conversion work.

View example

Review ConvertAPI usage for Affinity workflows

Retrieve ConvertAPI usage statistics on a schedule to review conversion activity during a specified date range.

Supported Triggers and Actions

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

Affinity triggers

Convertapi actions

Recurring trigger

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

TriggerScheduled

Async Convert

Starts an asynchronous file conversion.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Async Job

Deletes an asynchronous conversion job.

ActionInstant

Delete Uploaded File

Deletes an uploaded file from temporary storage.

ActionInstant

Check Conversion Support

Checks whether a specific file format conversion is supported.

ActionInstant

Get Supported Input Formats For Output

Lists input formats that can be converted to a chosen output format.

ActionInstant

Convert PDF to DOCX

Converts a PDF into an editable Word document.

ActionInstant

Convert PDF to JPG and Store

Converts a PDF into JPG pages and stores them on the server.

ActionInstant

Upload File From URL

Uploads a file directly from a remote location.

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.