- Home
- Resources
- Integrations
- Filestage
Filestage Zapier integrationAutomate Filestage with Zapier.
The Filestage Zapier integration gives you 17 triggers, 9 actions and 9 searches. 15 of those triggers are instant, Filestage is not a premium app, and it works on the free plan. Below: what each one does, what it costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Filestage Zapier integration actually does for you
The Filestage Zapier integration links your review and approval workspace to Zapier, so an event in Filestage (a comment, a decision, a new version, a new project) can start work on its own. You pick the event, you pick what follows, and the back-and-forth you used to do by hand runs without you.
Projects that set themselves up. Every time someone opens a project, Create Reviewer Group adds the group your process needs, and Add Reviewers to Reviewer Group fills it. Account managers stop rebuilding the same structure for each campaign.
Decisions nobody misses. When a Review Decision Is Submitted fires the moment a reviewer clicks Approve or Request changes. That is your cue to post a note with Create Review Comment or to move the work along.
A clean archive. Archive/Unarchive Project closes a project when the job is done, so the active list stays short.
What Zapier cannot do here: there is no action that approves a file or submits a decision in your place, and none that deletes a file or a project. Deletions only show up as triggers. Those calls stay with a human, inside Filestage.
If you are weighing tools, the Filestage Make integration covers the same app on Make, and n8n vs Zapier lays out the criteria side by side.
Zapier vocabulary in one minute
Eight words you will see on every screen of the editor. Read them once and the rest of the page goes faster.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
- Task
- What Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer by Zapier. An instant one is reported by the app itself, the moment the event happens.
- Filter
- A step that lets the Zap carry on only when what arrived matches your condition, and stops it there otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found.
- Connection
- Your Filestage account linked to Zapier once, then reused by every step of every Zap that touches Filestage.
What a Filestage Zap really costs
Zapier bills tasks, not triggers. A Filestage event that starts your Zap costs nothing; each action that goes through costs one task.
- TriggerNever costs a task
- Successful action1 task each
- Free plan100 tasks a month, two-step Zaps only
- Premium appNo, Filestage works on the free plan
A three-action Zap uses three times what a one-action Zap uses, and a failed action is not counted. The free plan gives you 100 tasks a month, but only two-step Zaps: one trigger, one action. Add a second action, a filter or a search and the Zap becomes multi-step, which needs a paid plan. The interval grid below only concerns the 2 polling triggers; the 15 instant ones fire straight away on every plan.
Connect Filestage to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an existing Filestage account before you start; Zapier does not create one for you.
- 02
Pick Filestage
Type Filestage in the search box of the dialog, select it, then click Add connection. A new tab opens on the Filestage side, where the rest of it happens.
- 03
Sign in and grant access
Log in to Filestage in that tab and grant Zapier access to your account. From then on, every Zap that touches Filestage reuses this connection, so you only do this once.
Your first Zap: every new project gets its reviewers
GoalWhen a project is created in Filestage, add a reviewer group to it and put the usual reviewers in it.
- 01
Build: choose the trigger
Start a new Zap, pick Filestage as the app and When a New Project Is Created as the event. Select your Filestage connection.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent projects of your account, so you map the next steps on a real one rather than a blank.
- 03
Add the reviewer group
Add Create Reviewer Group. Map the project from the trigger into Project ID and give the group a name, for example Client sign-off.
- 04
Fill the group
Add Add Reviewers to Reviewer Group and map the group created by the step above into Step ID. Two actions means a multi-step Zap: you need a paid plan.
- 05
Test, then Publish
Test each action once and check the result inside Filestage. Then click Publish: the Zap is on and reacts to the next project.
Filestage triggers: 17 events that can start a Zap
17 events start a Zap when something happens in Filestage, and 15 of them are instant: the app calls Zapier straight away, whatever your plan.
When a New Comment Is Created
Instant triggerIn Zapier“Triggers when a collaborator or a reviewer creates a comment.”
Starts your Zap each time a collaborator or a reviewer leaves a comment on a file. You get the comment to route wherever your team actually reads things.
When a Comment Reply Is Created
Instant triggerIn Zapier“Triggers when a collaborator or a reviewer creates a comment reply.”
Covers the other half of the conversation: a reply under an existing comment. Pair it with the trigger above if you want the whole discussion, not just the first word.
When a Review Due Date Has Arrived
Instant triggerIn Zapier“Triggers when the review due date has arrived.”
Goes off on the day a review is due. This is the deadline itself, not a change to it, which makes it the natural hook for reminders and follow-ups.
When a File Due Date Is Changed
Instant triggerIn Zapier“Triggers when a file due date is set or updated.”
Reacts when a file gets a due date or when someone moves it. A shifted deadline is often the first sign a schedule is slipping, and this trigger surfaces it.
When a File Is Deleted
Instant triggerIn Zapier“Triggers when a file and all its versions are removed.”
Fires when a file disappears from Filestage along with every one of its versions. Zapier offers no delete action for files, so this is the only way a Zap hears about it.
When a Review Is Started in a New Reviewer Group
Instant triggerIn Zapier“Triggers when a review is started in a new reviewer group.”
Picks up the moment a file moves into the next reviewer group and its review starts there. Think of it as the handoff from one round of feedback to the next.
When a File Review Status Is Changed (Depreciated)
Polling triggerIn Zapier“Triggers when a file review status is changed.”
An older version of the status trigger, still listed, with "Depreciated" in its name. It watches one project for a file whose review status moves.
When a File Version Is Deleted
Instant triggerIn Zapier“Triggers when a file version is removed.”
Notices when one version of a file is removed while the file itself stays. Useful when version history matters to you or to a client.
When a New Folder Is Created
Instant triggerIn Zapier“Triggers when a new folder is created.”
Runs as soon as someone adds a folder. Folders usually mark a new client or a new line of work, so this is a good place to start setup automations.
When a Reviewer Is Invited to a Reviewer Group
Instant triggerIn Zapier“Triggers when a reviewer is invited to a reviewer group.”
Tells you each time a person is invited into a reviewer group. You see who joins the review as it happens.
When a New File Is Added to a Project
Polling triggerIn Zapier“Triggers when a new file is added to a project.”
Spots a fresh file in a project you name. It is the trigger for anything that should happen when work lands for review.
When a New File Version Is Uploaded
Instant triggerIn Zapier“Triggers when a new version of a file is uploaded.”
Catches the upload of a new version of an existing file. Reviewers who already gave feedback usually want to know the corrected one is in.
When a Project Is Archived
Instant triggerIn Zapier“Triggers when a project is archived.”
Signals that a project has been put away. In most teams that means the job is done, which is the right time to close things elsewhere.
When a New Project Is Created
Instant triggerIn Zapier“Triggers when a new project is created.”
Starts a Zap every time a project appears in Filestage. It is the hook of the first Zap on this page, and the one to use for any repeatable setup.
When a Project Is Deleted
Instant triggerIn Zapier“Triggers when a project is removed.”
Lets you know a project is gone for good. Zapier has no action to delete a project, so this trigger is your only window on it.
When a File Review Status Is Changed
Instant triggerIn Zapier“Triggers when a file review status is changed.”
Follows a file as its review status moves on. This is the current, instant version of the status trigger, and unlike the old one it asks for no Project ID.
When a Review Decision Is Submitted
Instant triggerIn Zapier“Triggers when a reviewer submits a review decision by clicking either 'Request changes' or 'Approve'.”
Goes off when a reviewer clicks either Approve or Request changes. Unlike the status trigger, it is tied to one person deciding.
Filestage actions: 9 things a Zap can do for you
Filestage gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Reviewers to Reviewer Group
ActionIn Zapier“Adds reviewers to a chosen reviewer group.”
Puts people into an existing reviewer group, with the option to notify them by email and to ask them for a decision.
Archive/Unarchive Project
ActionIn Zapier“Archives/Unarchives a project by its ID.”
Puts a project away or brings it back, depending on the isArchived field you set. One action, both directions.
Create Folder
ActionIn Zapier“Creates a new folder in Filestage.”
Adds a folder with the name you give it. Only that name is required, so it is the simplest action of the set.
Create Project
ActionIn Zapier“Creates a new project in Filestage.”
Opens a new project inside a folder you choose, with the name you set. It is the base everything else hangs on.
Create Review Comment
ActionIn Zapier“Creates a general comment for a chosen review.”
Posts a general comment on a review, with an optional Team Only field.
Create Reviewer Group
ActionIn Zapier“Creates a new reviewer group.”
Builds a new reviewer group in a project. You can also decide whether its members may upload files.
Download File Version
ActionIn Zapier“Downloads the contents of the chosen file version.”
Pulls the content of one specific version of a file into the Zap, so the next steps can store or send it.
Upload a File
ActionIn Zapier“Uploads a file to a defined project by its URL.”
Sends a file into a reviewer group from a link, with the file name you choose. The link must be reachable by anyone.
Upload a File (With a File Object)
ActionIn Zapier“Uploads a file to a defined project.”
Uploads a file that an earlier step of the Zap already carries, rather than a public link. Handy when the source app hands over the file itself.
Filestage searches: 9 ways to fetch what already exists
9 search steps look for data that already exists in Filestage, so a later step can use it.
A search step looks something up in Filestage and hands it to the next step. In the editor, they sit at the bottom of the event list under SEARCH. Any search makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when the result is not what you expected.
Get Comments by Review
SearchIn Zapier“Returns all comments of a chosen review.”
Fetches every comment left on one review, so you can work with the whole discussion at once.
Get File by ID
SearchIn Zapier“Returns a file by its ID.”
Brings back a single file when you already hold its ID from an earlier step.
Get File Reviews
SearchIn Zapier“Returns all reviews of a file by its ID.”
Lists all the reviews a file went through, round after round.
Get Folders
SearchIn Zapier“Returns all folders of the team.”
Returns every folder of your team. No ID to supply, which makes it the easy starting point.
Get Folder by ID
SearchIn Zapier“Returns a folder by its ID.”
Looks up one folder from its ID, when you need its details rather than the whole list.
Get Projects
SearchIn Zapier“Returns all projects of the team.”
Pulls the full list of projects your team has, without any ID to enter.
Get Project by ID
SearchIn Zapier“Returns a project by its ID.”
Retrieves one project when its ID comes from a trigger or a previous step.
Get Review by ID
SearchIn Zapier“Returns a review by its ID.”
Fetches one review from its ID. It is the usual bridge before Create Review Comment.
Get Reviewer Groups by Project
SearchIn Zapier“Returns reviewer groups by project.”
Returns the reviewer groups of a project, which gives you the Step ID other actions ask for.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switch it on and the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into find-or-create. Filestage offers no find-or-create variant, so you will not use it with these searches.
- If multiple search results are found?Three ways out: keep the first match (the default), stop the Zap, or pass every match on at once.
When your Filestage Zap breaks
Zapier links no help article to Filestage and lists no rate limit for it. What breaks is the general mechanics, and they bite hard on a review tool where everything is linked.
Four cases to know before you switch anything on. If one of them hits you anyway, the Zapier troubleshooting page is the next stop.
No catch-up on old reviews
A Zap only reacts to what happens after you publish it. Comments, files and decisions from before stay where they are; moving them is a separate job.The Zap that triggers itself
Create Folder inside a Zap started by a new folder, or Archive/Unarchive Project after an archive trigger: the Zap sets itself off again and again and burns tasks.Bulk uploads held back
Drop a large batch of files or projects at once and Zapier's flood protection can hold the trigger back instead of running everything.Polling never runs twice
On the 2 polling triggers, Zapier remembers what it already saw, so the same item never starts the Zap twice.
Need help automating Filestage with Zapier?
A person reads every message.



