Connect Zendesk to Addresszen

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

View example

Check Addresszen access when a Zendesk user is created

Verify that the connected Addresszen API key is usable whenever a new Zendesk user appears.

View example

Resolve a saved address for a new Zendesk user

Use an Addresszen suggestion id stored in a new Zendesk user profile to return a complete US address.

View example

Audit Addresszen access during customer intake

Run a lightweight Addresszen key check for each newly created Zendesk customer record.

View example

Prepare a new user's address for shipping

Resolve a supplied Addresszen address id from a new Zendesk user so shipping staff receive a complete US address.

View example

Check Addresszen access when a ticket arrives

Verify Addresszen key availability whenever a new Zendesk ticket is created in the selected view.

View example

Resolve an address id from a Zendesk ticket

Find an Addresszen suggestion id in a new ticket and return the complete US address for the support team.

View example

Resolve delivery details for address support tickets

Resolve the Addresszen id included in a new delivery support ticket and provide the full US address.

View example

Flag Addresszen credential risk in the ticket queue

Check Addresszen key availability for every new ticket so credential problems are visible before address work begins.

View example

Resolve a customer location question from a ticket

Resolve a supplied Addresszen address id when a new Zendesk ticket asks about a customer's location.

Supported Triggers and Actions

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

Zendesk triggers

Addresszen actions

Recurring trigger

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

TriggerScheduled

Key Availability

Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.

ActionInstant

Webhook trigger

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

TriggerInstant

Resolve Address USA

Tool to resolve an address autocompletion by its address id and return the full address in us format. use after obtaining an address suggestion id from the autocomplete endpoint.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

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.