Connect Zendesk to Bigpicture io

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

View example

Enrich new Zendesk tickets with a company profile

When a Zendesk ticket arrives with a verified website domain, look up the company profile in Bigpicture io for faster, better-informed support.

View example

Find a company domain from a Zendesk ticket

Use the company name in a new Zendesk ticket to find likely domains in Bigpicture io, so follow-up research starts from a credible web address.

View example

Enrich every new Zendesk user with company data

When a Zendesk user is created with a confirmed email domain, retrieve the matching company profile in Bigpicture io.

View example

Discover likely company domains for new Zendesk users

Use a new Zendesk user's company name to find likely company domains in Bigpicture io for verification and enrichment.

View example

Identify a company from a ticket IP address

When a new Zendesk ticket includes an IP address, use Bigpicture io to look up the associated company for investigation context.

View example

Create an account brief for high context tickets

For new Zendesk tickets with a verified domain, retrieve a Bigpicture io company profile and summarize the context for the support owner.

View example

Build a verified profile for new customer users

When a new Zendesk user has a confirmed organization domain, retrieve detailed company data in Bigpicture io for onboarding context.

View example

Find company domains from an incoming research request

Accept a webhook containing a company name and use Bigpicture io to return likely domains for your research workflow.

View example

Enrich incoming domains with company research

Use a Notis webhook to send a confirmed website domain to Bigpicture io and receive a detailed company profile.

Supported Triggers and Actions

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

Zendesk triggers

Bigpicture io actions

Recurring trigger

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

TriggerScheduled

Company Find

Tool to lookup company data by domain name. use when you need detailed company profile by providing a website domain. use after confirming domain correctness.

ActionInstant

Webhook trigger

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

TriggerInstant

IP to Company Lookup

Tool to lookup company by ip address. use after obtaining an ip to get detailed company info.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Name to Domain Search

Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.

ActionInstant

New Zendesk Ticket

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

TriggerPolling

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.