Aproova with n8n: automate notifications, not the review
Send review events to n8n, filter them by folder or group, and build WhatsApp notifications with a link and thumbnail.
Written by the Aproova product team from the review flows we build and test in the application.
A well-organized review can still wait because nobody noticed the update. Automation solves the notification, not the approval itself.
Aproova sends the event. n8n decides whether to message a channel, update another service, or call an API.
Choose one useful event first
A new review, released version, comment, decision, or stage change can trigger different workflows. Sending every event to the same chat creates noise.
Start with the manual step the team repeats most, such as notifying a client about a released version.
Scope the automation
A webhook can be limited by folder, subfolder, or group. One client can feed a dedicated workflow while internal work follows another route.
Dynamic fields carry review, version, file, folder, actor, link, and thumbnail data into the request.
Test before sending WhatsApp media
Create an n8n Webhook, copy its production URL into Aproova, and confirm an HTTP 2xx response with a test delivery.
Validate that the thumbnail URL returns an image before sending media. If no preview is available, send text with the review link and keep the decision in Aproova.
Keep the fallback simple
Media delivery should check whether the thumbnail URL returns an image. A PDF or video URL should not be sent as image media.
When no thumbnail is available, send a text notification with the review link. The reviewer still reaches the correct content.
Questions people ask before setting up the workflow
Does Aproova send WhatsApp messages directly?
The webhook sends data to n8n or another service. WhatsApp delivery depends on the provider and workflow configured by the team.
Can a webhook be limited to one client?
Yes. Endpoint scope can be filtered by workspace folder, subfolder, or group.
How do I know whether delivery worked?
Send a test, confirm an HTTP 2xx response, and check the recent delivery history after activation.
Continue with these guides
Approval history: what a useful audit trail should record
Learn which versions, people, decisions, comments, dates, and access events belong in a creative approval history.
Read guide
Client review links: easy access without opening the whole workspace
Share the intended review, define identity and permissions, test the client view, and revoke links when access should end.
Read guide
How to review packaging and labels without missing a critical change
Organize packaging review across design, product, regulatory, and production teams while keeping every decision tied to a version.
Read guide
What Aproova does, from the first version to final approval
See how Aproova handles visual feedback, versions, review stages, client access, decisions, and integrations.
Read guide
Aproova and Trello integration: keep the work item on the card
Link an Aproova review to a Trello card, send version and decision updates, and move the card when approval status changes.
Read guide
How to review a large catalogue without losing track
Review long catalogues with page comments, clear owners, version history, and a recorded decision on the right PDF.
Read guide
How to compare creative versions without relying on memory
Use side-by-side and overlay comparison to check changes before approving the final artwork.
Read guide
Visual feedback that designers can act on
Mark the right area, write a clear request, and separate suggestions from changes that block approval.
Read guide
How to choose online proofing software without buying complexity
A practical comparison of reviewer access, visual feedback, versions, decisions, integrations, and pricing.
Read guide
An agency approval workflow that reviews internally before the client
Separate internal review from client approval while keeping files, versions, and decisions in one history.
Read guide
How to build a creative approval workflow people will actually use
A practical workflow for keeping the asset, feedback, current version, and final decision together.
Read guide
How to review a PDF with clients without scheduling another meeting
Use page-specific comments, clear versions, and one client link to review PDFs asynchronously.
Read guide
How to collect video feedback without chasing timestamps
A straightforward way to review video by frame, keep comments in context, and approve the right cut.
Read guide