Using Aligno

Zapier integration

Connect Aligno to Zapier and the rest of your stack reacts on its own when a client comments or signs off — no code needed.

What it does

Aligno is publicly listed in the Zapier app directory. A Zap starts from an Aligno trigger — a new comment, an approval decision, a new version — and sends it into any of the 9,000+ apps Zapier connects: post to a channel, create a task, add a spreadsheet row, send an invoice. Zaps can also write back to Aligno: create a project, add a webpage asset, or turn on a share link.

Events arrive in Zapier as they happen. Aligno delivers them through a durable queue that retries on transient failures, so a blip doesn't lose a sign-off.

Connect Aligno to Zapier

In Aligno, open Dashboard → Integrations, find the Zapier card, and click Configure → Generate key.
Copy the key immediately.It's shown exactly once — Aligno stores only a hash, so it can't be shown again. If you lose it, revoke it and generate a new one.
In Zapier, create a Zap and choose Aligno as the trigger app (or start from the directory listing).
When Zapier asks you to connect your Aligno account, paste the API key. The connection is labelled with your account email.
Pick a trigger, run Zapier's test step (it pulls a few recent real samples), add your action, and turn the Zap on.

Owner-only, like all integrations

API keys are created and revoked by the account owner. Team collaborators' activity (comments, approvals on shared work) still fires the owner's Zaps — see team collaboration.

Triggers

Each of these can start a Zap:

New Comment

A reviewer leaves a new comment or reply.

Approval Received

A reviewer approves an asset or requests changes.

New Asset

A new asset is added to a project.

New Asset Version

A new version is uploaded to an existing asset.

Comment Resolved

A comment is marked resolved.

New Project

A new project is created.

The Approval Received trigger fires only on real decisions — approved or changes requested — never on the pending state a new version starts in.

Actions

Create Project

Creates a new project.

Create Webpage Asset

Adds a webpage (by URL) as a new asset in a project for review.

Share Asset

Enables (or reconfigures) the public review link for an asset and returns its share URL.

Searches

Find Project

Finds a project by name (partial match).

Find Asset

Finds assets by name, optionally scoped to a project.

Find Asset Details

Finds an asset by ID, including current version and latest approval status.

Find Comments on Asset

Finds comments on an asset, optionally filtered by status.

Managing API keys

Keys live on the same Integrations page. Each shows its label, prefix, creation date, and when it was last used.
Every key is scoped to your own account — it can only ever read or write your own projects.
Revoking a key immediately disconnects the Zaps it created. Their subscriptions are removed so nothing keeps sending after you cut it off. To move to a fresh key, generate the new one first, reconnect your Zaps, then revoke the old one.

Beyond Zapier: the REST API

The Zapier app is built on Aligno's public REST API, and your key works there too. The interactive reference lives at /docs/api, and the raw OpenAPI spec at /api/v1/openapi.json.

Troubleshooting

The connection test fails. Check the key was pasted whole (it starts with algn_live_) and hasn't been revoked. Generate a fresh key if in doubt.
A Zap stopped firing. First check the key still exists on your Integrations page — revoked keys disconnect their Zaps. Then check the Zap is still on and look at its run history in Zapier.
Zap or workflow problems inside Zapier (editor errors, mapping issues, runs that error on the Zapier side) are best reported through Zapier's support— they can see your Zap's run details and route integration bugs to us directly.

Start Here