Connect Zendesk to Bigml
When something happens in Zendesk, Notis takes the next step in Bigml. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Zendesk to Bigml
Create a BigML project for every new Zendesk ticket theme
Group newly created Zendesk tickets into a BigML project for focused analysis.
Create a BigML project for new Zendesk user onboarding analysis
Start a BigML project when a new Zendesk user is created so onboarding patterns can be studied.
Create a BigML external connector for ticket analysis sources
Use each new Zendesk ticket to identify and create an external connector for its analysis source.
Create a BigML connector for new user data sources
When a Zendesk user profile identifies an approved data source, create its BigML external connector.
Inspect a BigML connector after a Zendesk data request
Retrieve external connector details when a new Zendesk ticket asks about a data connection.
Inspect a BigML connector linked to a new Zendesk user
Retrieve connector details when a new user record includes a known BigML connector reference.
Retrieve BigML project context for a new Zendesk ticket
Look up a referenced BigML project and summarize its metadata for the incoming ticket.
Retrieve BigML project context for a new Zendesk user
Look up a referenced BigML project when a new Zendesk user record contains project context.
List BigML correlations for a new support issue
Browse available BigML correlations when a new Zendesk ticket asks about relationships in data.
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Bigml. A trigger fires from one place; an action lands in another.
Zendesk triggers
Bigml actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create External Connector
Tool to create a new external connector for data sources. use after configuring external databases or search indices.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Project
Tool to create a new project. use when you need to group related bigml resources into a project.
New User Created
Triggered when a new user is created in Zendesk.
Delete Project
Tool to delete an existing project. use when you need to permanently remove a project resource after confirming it is not in use by other resources.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Get External Connector
Tool to retrieve details of an external connector. use after creating or listing external connectors to inspect its state.
Get Project
Tool to retrieve details of a project by id. use when you need to inspect project metadata before analysis.
List Correlations
Tool to list correlation resources. use when you need to browse or paginate existing correlations for the authenticated user.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Zendesk and Bigml
Connect any two apps with Notis in the middle.
Zendesk and Bigml, 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 Bigml.