Zapier & API

Automate what happens after a client responds

A comment lands or a client approves a version, and the rest of your stack should just know. Aligno triggers Zapier and thousands of apps on every review event, and exposes the same data through a REST API you can build on. Your clients still review with no login.

Triggers for every review event

Start a Zap when a client leaves a comment, resolves one, or makes an approval decision, and when a project, asset, or new version is created. Each event carries a clean, id-keyed payload so Zapier can dedupe and filter on it.

Real-time, not polling

Aligno delivers events to Zapier as they happen through a durable, at-least-once webhook queue. A transient failure retries with backoff instead of dropping the event, so your automations don't miss a sign-off.

A REST API you can build on

Read projects, assets, comments, and approvals, or create projects, webpage assets, and share links over a straightforward REST API. The full contract lives in an OpenAPI spec with interactive docs.

Scoped, revocable API keys

Generate an API key from your dashboard, shown once. Every key is scoped to your own account, and revoking one immediately tears down the Zaps it created so nothing keeps sending after you cut it off.

The moment a client signs off, a handful of little tasks usually follow. Someone updates the project tracker, the next stage kicks off, an invoice goes out. Wiring Aligno into Zapier or the API lets those happen on their own, the instant the decision is recorded, instead of waiting for you to notice and copy the update across. It slots into your design approval workflow rather than replacing it.

How it works

Connected in three steps

Step 1

Create an API key

From your dashboard integrations page, generate an Aligno API key. Copy it when it's shown, since it isn't stored in a way anyone can read back later.

Step 2

Connect Aligno in Zapier

Add Aligno to a Zap, paste your API key, and pick a trigger such as new comment or new approval. Zapier walks you through a test event.

Step 3

Send events anywhere

Route the trigger into any of Zapier's 7,000+ apps, or skip Zapier entirely and call the REST API directly from your own tools.

Your API keys are stored hashed, scoped to your account, and revocable at any time.

Questions

Frequently asked questions

What can trigger a Zap?
New client comments, resolved comments, and approval decisions, plus new projects, assets, and asset versions. You choose which trigger a Zap listens for, and each event is deduped by a stable id.
Is there a REST API as well as Zapier?
Yes. Zapier is built on the same public REST API you can use directly. It covers reads for projects, assets, comments, and approvals, and writes for creating projects, webpage assets, and share links. The contract is published as an OpenAPI spec with interactive docs.
Where do I find the API docs?
The interactive API reference is at /docs/api, and the raw OpenAPI spec is served at /api/v1/openapi.json. Both stay in sync with the endpoints your key can call.
How are API keys kept safe?
Keys are stored only as a hash, so the plaintext is shown to you exactly once and can't be recovered. Every key is scoped to your own account, and revoking a key also removes the Zapier subscriptions it created.
Do my clients need a Zapier account?
No. Automation is only for you. Clients still review through a no-account Aligno share link and never touch Zapier or the API.
Get started

Put client feedback on autopilot

Free plan available. Generate an API key, connect Zapier, and let clients review with no login.