Question 1

What can an automation do?

Accepted Answer

Read and write your database, call 50+ connected services such as Slack, Gmail, Stripe, HubSpot and Airtable, run AI to summarize or classify, render PDFs, and call any REST API. Automations are TypeScript, so branches, loops and parallel steps come with the language, and any npm package can be installed.

Question 2

Do I need to know how to code?

Accepted Answer

No. Describe what should happen and when, and Zite builds the automation, then lays out how it fires and each step it takes so you can read what it will do. You change it by asking. Zite builds each automation in TypeScript, so you get the full source code and GitHub sync.

Question 3

How does an automation start?

Accepted Answer

On a schedule, when its webhook URL is called, when a record in your database changes, from a button in one of your apps, or when something happens in another tool, like a new HubSpot contact or a Slack message. Zite connects the trigger when you publish, and nothing runs until you do. You can also test run it from the editor.

Question 4

What happens when one breaks?

Accepted Answer

A failed step retries on its own first. Every run is kept for 90 days with its steps, their inputs and outputs, anything they logged and the error if there was one. Filter the history down to the failed run, open it, and ask Zite what went wrong. Once it is fixed, resume the run from the step that failed, or replay it with the same inputs.

Question 5

Can I build automations from Claude Code or Cursor?

Accepted Answer

Yes. Connect your agent to Zite over MCP and it can read and edit an automation, check it, publish it and read its run logs. It runs on your own AI subscription, so it uses no Zite credits.

Question 6

Where does the code live?

Accepted Answer

In your workspace's git repository, next to your apps and database schema. Every change is a commit you can compare and restore, and you can sync the repository to GitHub so your developers can review it.

Question 7

What counts as an automation run?

Accepted Answer

One execution is one run, however many steps it has. Free includes 1,000 a month, Pro 5,000, Business 50,000 and Team 250,000. Runs from the editor are never counted, so testing costs nothing. If you do go over, what you have published keeps running; you just cannot publish edits until the month resets or you upgrade.

Question 8

Are scheduled automations on every plan?

Accepted Answer

Creating new scheduled tasks needs the Business plan. Webhooks, events from other tools, and test runs work on every plan including Free. Schedules you already have keep running if you move down a plan.

Automate any process with AI

Connect 50+ apps, or any API

Build it with AI, in real code

Build it with AI, in real code

Describe it

From Claude Code or Cursor

Real code underneath

Run it on infrastructure built for it

Run it on infrastructure built for it

Any trigger

Durable runs

Every change is a commit

See every step of every run

Automations teams run every day

Invoice every payment

Score and route new leads

Monday renewals digest

Turn emails into tickets

Daily metrics in Slack

Onboard a new hire

Sync orders to the ledger

Notes from every sales call

Chase unpaid invoices

Teams already running on Zite.

Questions about automations