FlowRunner
PricingContact
Theme
Start Free

Filestage

Project Management

Filestage is the review and approval platform for creative content. Agents create projects and sections, upload files and versions, invite reviewer groups, collect decisions and threaded comments with markers, pull review reports, and react to review events in real time.

Verified 1 trigger 78 actions API key available
Filestage website Platform Documentation Capability data verified 2026-08-24
A new asset version is exported from the design tool and lands in shared storage
Agent reads the campaign identifier the file was named with and resolves the matching project
Create Upload URL and Upload File push the version onto the existing file rather than creating a second one
Start Review pairs the new version with the first reviewer group in the chain
Set Review Due Date puts a deadline on the round so the reminder has something to hang off
The reviewers are invited by email address, no account or seat required
A named reviewer records the decision in Filestage, and the agent moves the chain forward only after it lands

What This Integration Enables

Filestage makes a structural choice that most approval tooling avoids: the reviewer is deliberately not a user. Anyone with a valid email address can be added to a reviewer group and asked for a decision, without an account and without consuming a seat, while team members hold seats and see the whole project. That single decision is why the approval chain in Filestage reaches the people who actually sign off on creative work, the client, the brand lead, the regulatory reviewer, rather than stopping at the boundary of who has a license. Reviewer groups run in sequence, which makes the chain an ordered object a flow can advance rather than a convention people are asked to remember.

FlowRunner agents operate everything around the decision. They build projects from templates that carry the standard sections and reviewer groups, push new versions onto existing files so the history stays intact, start reviews against the right group, set due dates, invite reviewers, read the comment stream with its markers and replies, pull review reports, and file the finished work. The connector is also honest about its asynchronous edges: uploads and website imports complete after the call returns, so flows use a callback rather than assuming the response means the asset is ready. What agents never do is record the decision itself, because a Filestage approval is a human-in-the-loop moment that only a named reviewer can honestly supply.

Without FlowRunner

Rounds chased by hand Someone follows up individually with each reviewer and keeps the status in their head
Feedback spread across replies Comments arrive in email threads, chat messages, and marked-up screenshots that never reach the file
Version confusion A reviewer approves a file while looking at the version before last

With FlowRunner

Rounds chased by the flow Due dates, reminders, and the handoff between reviewer groups run without anyone driving them
Feedback anchored to the asset Comments carry a marker on the image or a timecode on the video, on the version they were left against
One file, many versions A new export becomes a version of the existing file, so the review history stays in one place

Use Case Scenarios

  • A new export starts its own review round

    A designer exports a revision from Figma or Canva and it lands in Box or Dropbox. The agent reads the campaign code from the filename, resolves the project, and finds the existing asset with Find Files By External ID so the export becomes a new version rather than an orphan file. Because the bytes live inside FlowRunner rather than at a public address, it uses Create Upload URL to push them directly and then hands the result to Upload File with a callback so the flow knows when the version is genuinely ready. Start Review pairs the version with the first reviewer group, Set Review Due Date puts a deadline on the round, and the client reviewers get an email without anyone provisioning them an account.

  • Feedback that reaches the people who have to act on it

    While a round is open, the agent reads List Review Comments and separates comments carrying markers on the asset from general remarks, and internal team-only notes from anything the client can see. It groups the actionable items by section and posts them to the studio channel in Slack with the file and the timecode or coordinate attached. When a comment is addressed, Resolve Comment ticks it off in Filestage so the reviewer sees their point was handled. Where the same feedback applies to a sibling asset, Copy Comments carries it across versions or reviewer groups instead of someone retyping it.

  • The round that closes itself and files the evidence

    When a reviewer group finishes, the On Filestage Event trigger fires. The agent calls Count Section Review Decisions for a cheap progress read, and if the group has cleared, advances the asset to the next reviewer group in the chain. Once the final group is done it calls Download Review Report and Download File Report, stores the approval record alongside the deliverable, updates the campaign task in Asana or Monday.com, and moves the project into the archive folder with Move Project To Folder. The approval trail exists as a document rather than as a memory of who said yes in a meeting.

Human-in-Loop Highlight

Filestage exists to collect a human decision, which makes one operation in this connector genuinely dangerous in a way the others are not. Update Review Status sets a review's status directly, bypassing the decision flow entirely, and Submit Review Decision records an approval against a review. An agent holding those two calls can mark creative approved that no person ever looked at, and the record will be indistinguishable from a real sign-off. Undo Review Decision is not a safety net: Filestage allows it for about thirty seconds after the fact, which makes it a correction for a misclick rather than a way back.

So FlowRunner agents do not record decisions on anyone's behalf. They prepare the round, chase it, read it, and report it, and the approval itself is left to the named reviewer inside Filestage where it belongs. The one place a flow touches review state is administrative, moving a stalled round into a team's own custom status such as awaiting legal, and even that asks first: "Round 2 on hero-video-v4 has been open 9 days. Two of four reviewers have decided, both approved. Move the review to Awaiting Legal, extend the due date, or send a reminder?" The producer picks. Nothing in that exchange is the agent deciding the creative is good. The other hard stop is Remove Team Member, where the force flag takes the person's webhooks and API keys with them and the review-access flag strips them from every project's reviewer groups, which is a set of consequences no offboarding script should choose unattended.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

78 actions

Folders

4
  • List Folders Returns every folder in the team. Folders are the top of the hierarchy, so this is where a flow starts when it needs somewhere to create a project.
  • Get Folder Returns one folder with its name and parent.
  • Create Folder Creates a folder, optionally inside an existing one. Filestage allows two levels below the root, so a parent that is already a subfolder is refused.
  • Delete Folder Deletes a folder, but only an empty one. Filestage refuses rather than deleting recursively, which makes this a safe cleanup operation.

Projects

9
  • List Projects Returns the team's projects, optionally narrowed to one folder. A project holds sections, reviewer groups, files, and collaborators.
  • Get Project Returns one project with its folder, archive state, collaborators, and sections.
  • Create Project Creates a project inside a folder, optionally from a template and optionally inviting collaborators in the same call. Building from a template is what carries the standard reviewer chain across.
  • Rename Project Changes a project's name. Its file and review identifiers are untouched, so nothing downstream breaks.
  • Move Project To Folder Moves a project into a different folder. Used to file completed work away without archiving it.
  • Archive Project Archives or unarchives a project, hiding it from the active list while keeping every file, review, and comment. The reversible alternative to deletion, and the default in cleanup flows.
  • Delete Project Permanently deletes a project with its files, reviews, and comments. Reviewed before it runs, since archiving is almost always what was meant.
  • Add Project Collaborators Invites people to a project by email address. A collaborator sees the whole project, unlike a reviewer, who is added to a single group.
  • Remove Project Collaborator Removes one collaborator from a project, leaving their team membership and reviewer access elsewhere untouched.

Sections

6
  • Add Section Adds a section to a project. Sections group files inside a project, so this is how a large campaign is split into named parts.
  • Rename Section Changes a section's name. The files inside are untouched.
  • Move Section Reorders a section within its project, using a zero based position within the project's existing section count.
  • Delete Section Removes a section from a project.
  • List Section Files Returns the files inside one section. Used to check completeness before a round opens.
  • Count Section Review Decisions Returns how many reviews in a section sit at each status. The cheap read behind a progress dashboard, because the counts are grouped for you rather than assembled from the reviews.

Reviewer Groups

10
  • List Reviewer Groups Returns the reviewer groups of a project. Filestage calls a reviewer group a step on the wire, so the identifier a review needs is a step identifier.
  • Get Reviewer Group Returns one reviewer group with its reviewers and settings.
  • Create Reviewer Group Adds a reviewer group to a project, optionally inviting reviewers and setting permissions in the same call. Groups run in sequence, which is how an approval chain is built.
  • Rename Reviewer Group Changes a reviewer group's name, leaving its reviewers, settings, and reviews untouched.
  • Update Reviewer Group Settings Sets what reviewers may do at each review status. Permissions are per status, so turning off commenting after approval does not affect commenting before it.
  • Add Reviewers Invites reviewers to a group by email address. No Filestage account and no seat is required, which is what makes this usable with clients, and requesting a decision asks each of them for an explicit approval rather than comments alone.
  • Remove Reviewer Removes a reviewer from a group, identified by their identifier or by email address.
  • List Reviewer Group Reviews Returns the reviews in one group. The only paginated collection in the API, and it continues by page token rather than page number.
  • Get Mention Suggestions Returns the users who can be mentioned in a comment on this group, with the identifier a mention needs. Called before writing a comment that tags someone.
  • Delete Reviewer Group Deletes a reviewer group together with its reviewers, and the reviews already made in it go too.

Files

13
  • List Project Files Returns every file in a project with its versions.
  • Get File Returns one file with its versions and the section it sits in.
  • Find Files By External ID Looks up files by the identifier your own system stored on them, which is how a flow finds the Filestage file matching one of its records. Filestage does not enforce uniqueness on that field, so a match set is checked before anything acts on it.
  • Upload File Adds a file to a project or to specific reviewer groups by giving Filestage a URL to fetch. The upload is asynchronous, so flows supply a callback rather than treating the response as completion, and naming an existing file adds a version instead of creating a duplicate.
  • Create Upload URL Generates a presigned URL to push bytes directly, plus the address to hand back afterwards. The path to use when the file exists only inside FlowRunner and has no public URL.
  • Import Website Adds a live website to a project as a reviewable asset. Asynchronous like the file upload, and the viewer mode decides how the site is presented to reviewers.
  • Move File To Section Moves a file into a different section of its project.
  • List File Reviews Returns every review of a file, one per reviewer group it has been through, optionally narrowed to one group.
  • Find File Reviews By External ID Returns the reviews of the file carrying a given external identifier, so a flow can check approval progress using its own key.
  • Download File Version Downloads the original bytes of one file version into FlowRunner file storage and returns a URL later steps can use. A version imported as a website cannot be downloaded.
  • Get File Version URL Returns a direct URL to one version's stored data, for handing to a downstream system that fetches the bytes itself.
  • Delete File Permanently deletes a file with every version, review, and comment on it.
  • Delete File By External ID Permanently deletes the file carrying a given external identifier. Since that field is not unique, a flow confirms exactly one file matches before calling it.

Reviews

8
  • Start Review Starts a review by pairing one file version with one reviewer group, which is what puts the asset in front of those reviewers.
  • Get Review Returns one review with its status, due date, and every reviewer's decision. The read behind any progress report.
  • Submit Review Decision Submits an approval decision on a review. The single modern route, replacing the vendor's four deprecated per-outcome endpoints, and the operation FlowRunner agents leave to a named person.
  • Undo Review Decision Revokes a decision within roughly thirty seconds of it being made. A correction for a misclick rather than a general reset.
  • Update Review Status Sets a review's status directly, bypassing the decision flow. It accepts a built-in status or one of the team's custom statuses, and it is gated behind a person for exactly that reason.
  • Set Review Due Date Sets a review's deadline. Filestage emits its due date event when the moment arrives, which is what a reminder flow hangs off.
  • Download Review Report Generates a report for one review and stores it in FlowRunner file storage. Produced for images, videos, documents, and websites.
  • Download File Report Generates a report covering every review left on a file and stores it in FlowRunner file storage. The artifact that becomes the approval record for an asset.

Comments

10
  • List Review Comments Returns every comment on a review, including replies and their markers.
  • Create Review Comment Adds a comment to a review. A marker positions it on the asset, a point on an image or a timecode on a video, and a team-only comment stays invisible to external reviewers.
  • Copy Comments Copies comments from one review to another, either between two versions of the same file or between two reviewer groups, so repeated feedback is not retyped.
  • Get Comment Returns one comment with its author, resolution state, and replies.
  • Update Comment Edits a comment's text and optionally its team-only visibility.
  • Reply To Comment Adds a threaded reply. Replies inherit the parent's position on the asset, so no marker is needed.
  • Resolve Comment Marks a comment complete or reopens it. This is how a reviewer sees their feedback was actioned rather than ignored.
  • Pin Comment Pins a comment to the top of the list, or unpins it. Used to keep the blocking note visible.
  • Download Comment Attachment Downloads a file attached to a comment into FlowRunner file storage and returns a URL later steps can use.
  • Delete Comment Permanently deletes a comment and its replies.

Team

8
  • List Team Roles Returns the roles available in the team with the identifier the invite and role operations require. Called first, since the identifier is not guessable from the name.
  • List Team Members Returns the team's members with their roles. A team member holds a seat, unlike a reviewer.
  • Invite Team Member Adds one person to the team with a role, which consumes a seat. Bringing someone into a single project without a seat is done by adding them as a reviewer instead.
  • Invite Team Members Adds several people with one shared role and emails their invitations. Filestage routes this through an existing member as the inviter.
  • Update Team Member Email Changes a team member's email address, supplied alongside their current one.
  • Update Team Member Role Changes a member's role, which is how permissions are granted or withdrawn without removing the person.
  • Remove Team Member Removes someone from the team. The force flag takes their webhooks and API keys with them, and the review-access flag strips them from every project's reviewer groups, so offboarding flows state both explicitly and confirm before running.
  • Remove Team Member By Email Removes someone by email address or identity provider identifier, for a flow that knows the person but not their Filestage identifier. The same two flags apply.

Project Templates

6
  • List Project Templates Returns the team's project templates. A template carries sections and reviewer groups.
  • Create Project Template Creates an empty project template, to be filled with sections and reviewer groups and then referenced when projects are created.
  • Rename Project Template Changes a template's name. Projects already built from it are untouched.
  • Add Template Section Adds a section to a template, so every project built from it starts with that section.
  • Add Template Reviewer Group Adds a reviewer group with its permission settings to a template. This is how a standard approval chain is defined once and reused.
  • Delete Project Template Deletes a template. Projects already built from it are untouched.

Webhooks

4
  • List Webhooks Returns every webhook registered on the team, including those created by FlowRunner triggers. Used to audit what is subscribed before adding more.
  • Create Webhook Registers a webhook for delivering events to a system other than FlowRunner. Deliveries arrive from a fixed set of addresses a firewall must allow, and a failed delivery is retried only once. A flow that wants the events itself uses the On Filestage Event trigger instead.
  • Update Webhook Changes a webhook's address, event list, or delivery headers. The event list replaces the stored one rather than adding to it.
  • Delete Webhook Removes a webhook from the team, stopping its deliveries.

Triggers

1 triggers

Event Triggers

1
  • On Filestage Event Fires when Filestage reports the chosen event, or every event the team emits. This is what lets a decision, a comment, or a due date arriving start a flow rather than sit until someone checks. Filestage retries a failed delivery only once, so flows that must not miss an event pair the trigger with a periodic reconciliation read.

Frequently Asked Questions

What can FlowRunner do with Filestage?

FlowRunner agents can run List Folders, Get Folder, and Create Folder in Filestage, plus 75 more actions.

Does connecting Filestage to FlowRunner require OAuth?

No. Filestage connects to FlowRunner with an API key, no OAuth flow required.

Can Filestage trigger a FlowRunner workflow automatically?

Yes. Filestage supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Filestage

Free plan, no card required. Connect in minutes.