Connect Zendesk to Salesforce

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

View example

Turn Zendesk tickets into Salesforce follow-up tasks

Create a Salesforce task when a new Zendesk ticket needs a customer follow-up, with the ticket context ready to act on.

View example

Add new Zendesk users as Salesforce contacts

Create a Salesforce contact when a Zendesk user is created, using the available user details to reduce duplicate entry.

View example

Capture ticket sales inquiries as Salesforce leads

Create a Salesforce lead when a new Zendesk ticket clearly signals a sales inquiry and includes the required lead details.

View example

Save ticket context to a Salesforce record

Create a Salesforce note from a Zendesk ticket when you provide the Salesforce record reference to attach it to.

View example

Create Salesforce onboarding tasks for new Zendesk users

Create a Salesforce task for a new Zendesk user when your team needs to take a specific onboarding step.

View example

Create Salesforce opportunities from qualified ticket inquiries

Create a Salesforce opportunity from a Zendesk ticket when it contains a qualified deal and the required opportunity details.

Supported Triggers and Actions

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

Zendesk triggers

Salesforce actions

Recurring trigger

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

TriggerScheduled

Create Salesforce Account

Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.

ActionInstant

Webhook trigger

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

TriggerInstant

Add contact to campaign

Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Add lead to campaign

Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.

ActionInstant

New Zendesk Ticket

Triggers when a new ticket is created in a specified Zendesk view.

TriggerPolling

Add product to opportunity

Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.

ActionInstant

Apply lead assignment rules

Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.

ActionInstant

Associate contact to account

Associates a contact with an account by updating the contact's accountid field.

ActionInstant

Clone opportunity with products

Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.

ActionInstant

Clone record

Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.

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.