Connect Affinity to Dropbox sign

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

View example

Send an investor NDA when a deal is ready

Start an NDA signature request from an Affinity deal update, with the investor and deal context included in the instruction.

View example

Review open investor signature requests

On a schedule, check Dropbox Sign requests against deal context supplied from Affinity and surface what still needs attention.

View example

Prepare embedded signing for an investor

Use a webhook with deal and signer context to create an embedded Dropbox Sign request from an existing template.

View example

Request a monthly signature status report

Request a Dropbox Sign document status CSV on a schedule to support a recurring review of Affinity deal paperwork.

View example

Batch send approved investor agreements

When Affinity deal context identifies a ready group, use Dropbox Sign bulk send with a specified template for up to 250 requests.

View example

Stage an investor agreement for later completion

Create an unclaimed Dropbox Sign draft from deal context so a teammate can claim and finalize it later.

View example

Check progress on investor bulk sends

Review Dropbox Sign bulk send jobs on a schedule and summarize progress against deal context supplied from Affinity.

View example

Create a reusable investor agreement template

Turn an approved agreement and signer-role details provided with a deal handoff into a Dropbox Sign template.

View example

Check signature status for priority deals

On a schedule, retrieve status for specified Dropbox Sign requests tied to priority Affinity deals and report the next follow-up.

Supported Triggers and Actions

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

Affinity triggers

Dropbox sign actions

Recurring trigger

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

TriggerScheduled

Invite User to Team

Invite a user to join your team.

ActionInstant

Webhook trigger

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

TriggerInstant

Add User to Template

Grant an account access to a template.

ActionInstant

Bulk create embedded signature request with template

Create a bulk job for embedded template-based signature requests.

ActionInstant

Bulk send with template

Create a bulk job to send template-based signature requests.

ActionInstant

Cancel Signature Request

Cancel a pending signature request asynchronously; once canceled, it cannot be restored.

ActionInstant

Create Dropbox Sign Account

Create a new account associated with an email address.

ActionInstant

Create API App

ActionInstant

Create Embedded Signature Request

Create a signature request for signing within an embedded frame.

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.