Skip to content
Notis

Make the signed-contract handoff easy to track

Mark the contract signed in Notion and let Notis create the next Close task for a smooth customer handoff.

Trigger

Page Properties Updated

Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.

Action

Create Task

This tool creates a new task in close.com. tasks are used to track to-do items and can be associated with leads. the tool will create a task with the specified parameters using the provided text, due date, and is complete flags.

Why this helps

Signing is a milestone, but the welcome message or handoff can get lost in the rush to the next deal.

  • Give a signed deal a defined next action.
  • Keep handoff details connected to the deal.
  • Reduce dropped steps after a sales milestone.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Close to Notis once in the portal.
  • 2Create an automation in Automations or describe it to Notis from a connected channel.
  • 3Use one plain-language instruction to create a Close task when a deal status changes to signed, describing the agreed handoff or next communication.
  • 4Pick Page Properties Updated, choose a channel for reports, and test with one signed-deal record.

Questions about this workflow

Can I choose the post-signature task?

Yes. State the desired customer communication or handoff step in the prompt.

Can this run only when a deal becomes signed?

Tell Notis to act on that status transition only and scope the trigger to the deal data source.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Close actions

Recurring trigger

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

TriggerScheduled

Create SMS Message

This tool creates a new sms message in close. the tool allows sending immediate sms messages or logging received sms messages using the provided phone numbers and message content. it includes parameters such as local phone, remote phone, text, status, and source.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Call

Creates a new call record in close.com. this tool allows you to log both inbound and outbound calls associated with a lead, supporting parameters such as lead id, direction, and optional support for contact id, phone, duration, note, recording url, and user id.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Create Lead

This tool creates a new lead in close crm. it allows users to create a lead with basic company information and optional contact details, including company name, description, website url, lead status, contacts, and addresses. it operates by sending a request to the api endpoint /lead/ on the close crm platform.

ActionInstant

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.

TriggerInstant

Create Task

This tool creates a new task in close.com. tasks are used to track to-do items and can be associated with leads. the tool will create a task with the specified parameters using the provided text, due date, and is complete flags.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Delete Call

This tool allows you to delete a specific call activity in close.com. it is useful for removing incorrectly logged calls or cleaning up call records. the action deletes a call activity using its unique call id and cannot be undone.

ActionInstant

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.

TriggerInstant

Get Notes

This tool retrieves a list of note activities from close. it allows users to fetch notes with optional filtering parameters, including filtering by lead id, user id, and date ranges. the tool returns details such as note content, creation and update dates, and any associated attachments.

ActionInstant

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.

TriggerInstant

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.

TriggerInstant

Connect any two apps with Notis in the middle.

Notion and Close, 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 Close.