Connect 2chat to Basin

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

View example

Create a Basin intake form from a launch brief

Send a form brief to Notis and have it create a Basin form with the requested name, timezone, and project association.

View example

Create a Basin project from a launch request

Start a Basin project when a launch request arrives, giving related forms a dedicated organizational container.

View example

Add a Basin form webhook after endpoint confirmation

When a confirmed callback URL and form ID arrive in a request, add a webhook to the specified Basin form.

View example

Set up a Basin submission notification destination

Create a Basin notification webhook when a verified external destination is submitted for form notifications.

View example

Review your Basin form inventory on a schedule

Have Notis periodically retrieve the Basin forms list and report the results so you can review your current form inventory.

View example

Review Basin projects on a recurring schedule

Periodically retrieve your Basin project inventory and send a concise report for review.

View example

Check configured Basin domains regularly

Retrieve your Basin account's configured domains on a schedule and report the results for a regular review.

View example

Retrieve Basin submissions when a review is requested

Use an incoming review request with a form ID to retrieve that form's Basin submissions for analysis or follow-up.

View example

Review Basin form metadata on a schedule

Periodically retrieve each form's details for a metadata review, using the forms list to identify which forms to inspect.

Supported Triggers and Actions

Notis builds workflows that link 2chat to Basin. A trigger fires from one place; an action lands in another.

2chat triggers

Basin actions

Recurring trigger

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

TriggerScheduled

Create Form

Tool to create a new form in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Form Webhook

Tool to create a new webhook for a specific form. use when you need to programmatically add a webhook once you have the form id and callback url confirmed.

ActionInstant

Create Notification

Tool to create a new notification webhook. use when you need to forward form submissions to an external service.

ActionInstant

Create Project

Tool to create a new basin project. use when you need a new organizational container for forms. example: "create a project named marketing leads."

ActionInstant

Delete Form

Tool to delete a form. use when permanently removing a form after it's no longer needed. ensure the form id is correct; this operation is irreversible.

ActionInstant

Delete Integration

Tool to delete a form webhook integration. use when removing an obsolete integration by id.

ActionInstant

Delete Project

Tool to delete a project. use when you need to remove a project after confirming its id. returns the deleted project's details.

ActionInstant

Delete Webhook

Tool to delete a specific webhook. use when you need to remove a webhook from a form after confirming its id.

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.