Move new prospect intake from Notion into Agencyzoom
Capture an inquiry once in Notion and let Notis create its Agencyzoom lead, keeping the next step close to where your sales work happens.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create lead
Creates a new lead or updates an existing one in agencyzoom; ensure `pipelineid`, `stageid`, `leadsourceid`, and `assignto` reference valid, existing entities.
Why this helps
A promising inquiry can sit unnoticed when intake details live in one workspace and the sales pipeline lives somewhere else.
- Reduce repeated entry between intake and sales systems.
- Get new prospects into the Agencyzoom pipeline sooner.
- Keep attention on the conversation instead of copying details.
Setup
Build it in a few focused steps.
- 1Connect Notion and Agencyzoom to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create one in plain language.
- 3In one instruction, say to create an Agencyzoom lead from each new Notion database page, using the page details and existing Agencyzoom records where needed.
- 4Select the Notion New Page trigger and choose where Notis should report runs.
- 5Test with one real intake page and check the resulting lead in Agencyzoom.
Questions about this workflow
Which Notion pages start this workflow?
Choose the New Page trigger for the Notion database where intake pages are created.
Do I have to set up field mappings?
No. Describe the intended result in one plain-language instruction, and Notis interprets the available page context.
What should I verify during the first run?
Check that the lead is associated with the intended Agencyzoom pipeline, stage, source, and assignee.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Agencyzoom. A trigger fires from one place; an action lands in another.
Notion triggers
Agencyzoom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authenticate for JWT via V4 SSO
Authenticates a user via v4 single sign-on (sso) using the provided callback `code` (typically required for success) to retrieve a jwt and initial user session information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Batch create contacts
Creates 1 to 5 new contacts in agencyzoom in a single batch api call.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Batch create leads
Creates up to 5 new leads in agencyzoom; all referenced entity ids (e.g., pipeline, user, custom field names) must exist, and organization `name` is required if `isbusiness` is true.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Batch delete tasks
Deletes multiple agencyzoom tasks in a batch; task deletion is permanent and the response indicates overall batch success, not individual task status.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Change lead status
Updates a lead's lifecycle status (e.g., active, won, lost, x-dated) and can optionally manage its workflow, pipeline, stage, source, or associated tags.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Mark task as completed
Marks an existing and accessible task in agencyzoom as 'completed'; this action does not return the full updated task object.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Create a customer note
Adds a new note to an existing customer's profile using their id; cannot be used to edit or retrieve existing notes.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Create a driver for an opportunity
Creates a new driver record associated with an existing agencyzoom opportunity using its id; full driver details are handled by the api endpoint directly, not specified in this action's request.
Connect any two apps with Notis in the middle.
Notion and Agencyzoom, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Agencyzoom.