New Linear Issue Becomes Close Task
Automatically create a task in Close when a new issue is created in Linear.
From your messaging apps, create Close leads, log calls and emails, update opportunities, and look up sales records by voice or text.
Mailchimp
Close
Drive it by message when you need it, or put it on autopilot.
Turn a voice memo or forwarded email into a Close lead, call record, email activity, or note.
Change opportunity details from chat. Try, "Update the Acme opportunity to the new amount and status."
Notis looks up Close records and replies. Ask, "Which opportunities are open for Acme?"
Get scheduled summaries of Close leads, opportunities, tasks, and sales activities delivered to your messages.
When a lead changes status or an opportunity changes status, Notis can respond with a message or workflow.
Pair Close with Gmail, Slack, or Google Sheets to carry sales updates across the tools your team uses.
Pick the channel you already live in. Notis turns it into a fully native Close remote.
Telegram
Voice-first Close bot. Record, tag, file.
WhatsApp business or personal, both work.
Slack
Slash-command your way through any workspace.
iMessage
Native bubbles. iPhone, iPad and Mac.
Gmail
Forward emails. Get them filed in Close.
Notis Desktop
Run from Notis desktop with hotkeys & history.
New Linear Issue Becomes Close Task
Automatically create a task in Close when a new issue is created in Linear.
Turn a Notion prospect into a Close lead
Create a Close lead when a new Notion database item contains a qualified prospect, so promising contacts do not stay buried in a research table.
Turn Slack prospect mentions into Close follow-ups
Create a Close task when a teammate shares a clear prospect follow-up in a Slack channel, so the next step is captured while the conversation is fresh.
Turn a Telegram inquiry into a Close lead
Capture a new sales inquiry sent to your Telegram bot as a lead in Close, so promising conversations have a clear home.
Remind me about stale Close leads
Review Close leads on a schedule and create Slack reminders for follow-ups that appear overdue.
Turn a qualified Close lead into a Linear issue
Send a qualified lead handoff from Close into a Linear project so product or customer teams can act without losing sales context.
Notis builds workflows that link this app to anything else. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Triggers when a bulk delete finishes.
Triggers when a bulk delete starts.
Triggers as a bulk delete progresses and reports how many records it has handled so far.
Triggers when a bulk edit finishes.
Triggers when a bulk edit starts.
Triggers when a bulk edit makes progress, with the number of records handled so far.
Triggers when a bulk email send starts.
Triggers when a bulk email send is paused by a person or by Close itself.
Triggers when a bulk email send makes progress, with the number of recipients handled so far.
Triggers when a bulk sequence action finishes.
Triggers when a bulk subscribe, pause, or resume action for a sequence starts.
Triggers when a bulk sequence action makes progress, with the number of contacts handled so far.
Triggers when a call is deleted from a lead’s timeline.
Triggers when a call is recorded on a lead, whether placed live or logged afterward.
The trigger fires when a call is recorded on a lead, whether the call was placed through the service or logged after it happened. The event can be filtered to include inbound calls only.
Triggers when a recorded call changes, including its note, outcome, recording, or transcript.
This event fires when a recorded call changes, for example when its note or outcome changes, or its recording or transcript changes.
Triggers when someone comments on an activity or object.
This event fires when a comment is posted on an activity or object. If it is the first comment on an object, that comment also opens a thread, triggering the thread-started event in the same request.
Triggers when a custom activity instance is deleted from a lead.
Triggers when a custom activity is logged on a lead.
Triggers when an existing custom activity instance changes.
Triggers when an email is deleted from a lead’s timeline.
Triggers when an email is recorded on a lead, whether received, drafted, scheduled, or logged as sent.
Triggers when an email thread is deleted from a lead.
Triggers when a new email thread appears on a lead; individual messages use a separate trigger.
Triggers when an email thread changes, such as when a message is added or its subject changes.
Triggers when a recorded email changes, such as an edited draft, a recorded open, or a status change.
This event fires when a recorded email changes, for example when a draft is edited, an open is recorded, or its status changes.
Triggers when the “Lead Created” entry appears in a lead’s timeline.
This event fires when the “Lead Created” entry is added to a lead’s timeline. It fires alongside the lead-created event for the same lead and includes the entry’s position in the timeline and the import that produced it.
Triggers when a Lead Created entry is removed from a lead’s timeline because the lead was deleted.
Triggers when a lead’s creation entry moves to another lead, usually after a merge.
Triggers when a lead changes status, alongside the general lead-updated event.
Triggers when a lead status change entry is removed from its timeline.
Triggers when a rapid second lead status change is folded into an existing timeline entry.
This event fires when a further status change is folded into an existing lead status change entry. This happens when the lead changes status twice in quick succession.
Triggers when a note is written on a lead.
Triggers when a note is deleted from a lead.
Triggers when an existing note is edited.
Triggers when an opportunity changes status.
Triggers when an opportunity status change entry is removed from a lead’s timeline.
A folded status change updates an existing opportunity timeline entry.
Triggers when a further status change is folded into an existing opportunity status change entry on the timeline.
Triggers when an SMS is deleted from a lead’s timeline.
Triggers when an SMS is recorded on a lead.
Triggers when a recorded SMS changes, such as when its status moves or a delivery error is recorded.
Triggers when a task-completed entry is removed from a lead’s timeline.
A lead timeline logs task completion; the task also emits its own completion event.
Triggers when a task-completed entry appears on a lead’s timeline. The task itself also fires its own completion trigger.
Triggers when a WhatsApp message is deleted from a lead’s timeline.
Triggers when a WhatsApp message is recorded on a lead.
Triggers when a recorded WhatsApp message changes.
Choose the app that starts the workflow and the app that should react. Notis sits in between, reading each event, deciding what matters, and writing the result exactly where it belongs.
When this happens · Trigger
Do this · Action
Popular pairs
Start with a managed app, then go beyond the catalog with any MCP server, any CLI tool, or one of 3,900+ tools and APIs you never sign up for at all. Notis uses all of them from the same conversation.
Choose a supported app and connect it in one click. Notis handles access and makes its actions available to every agent.
Browse integrationsBring any remote or local Model Context Protocol server. Its tools become available to Notis like any managed integration.
Set up a custom MCPUse any Linux command line on your Cloud Computer. Notis can install it, run it, and bring the result back to your conversation.
Install a CLI toolSemrush, Apollo, Apify and more are already wired in. No account, no API key, no subscription: each call comes out of your plan.
Browse pay-per-use toolsConnect in 60 seconds. No DIY, no maintenance, no setup tax.