A Filestack MCP that carries the transformation grammar, not a menu of endpoints
Connect one Filestack API key and app secret and 23 nodes land on the canvas: ingest a file by URL, read its metadata, mint a signed transformation link that costs nothing to build, run a chain and store the result, and put OCR, tagging, captioning, safe-for-work checks and sentiment analysis in front of anything a person uploaded. An agent can look at a file, decide what it is, and hand the next step a link rather than a blob.
What the Filestack MCP connector does
The Filestack connector for Mattering Automations is 23 nodes across four of Filestack's surfaces: the File API (metadata, a capped download, ingest by URL, overwrite, delete), the URL transformation grammar (build a signed link, run a chain and store the result, run a chain that answers with JSON), five typed convenience chains (format conversion, web page screenshot, zip, image size, PDF info), eight Intelligence tasks (OCR, image tagging, safe-for-work, captioning, image sentiment, text sentiment, document detection, face detection) and both Workflows endpoints. Fifteen nodes read, eight act, and exactly two are flagged destructive.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent handed a new upload can read what it is with Filestack: Get File Metadata, decide whether it is publishable with Filestack: Check Image Safe For Work, describe it for alt text with Filestack: Caption Image, and hand the next step a time-limited share link from Filestack: Build Transform URL, without anyone opening the Filestack dashboard.
One structural fact about Filestack shapes the whole connector, and it is worth explaining rather than hiding, because it is also the honest answer to why the node count is 23 rather than 70. Filestack's Processing API is not a list of endpoints. It is a URL grammar: about seventy named tasks that are written into the path and COMPOSE, so resize then compress then output is one request and one rendered result. A connector that shipped one node per task would ship a palette that cannot express a chain at all, because each node would make its own billed round trip to produce what Filestack renders in one. So the grammar is modelled by what comes back instead: Filestack: Build Transform URL signs a link and makes no call, Filestack: Transform And Store runs the chain and persists the result, and Filestack: Transform To JSON runs a chain whose last task already answers with data. On top of that sit the five typed chains and the eight Intelligence tasks, which are the parts of the grammar that genuinely are endpoint-shaped: a fixed task name, a documented JSON response, and a capability somebody looks for by name.
The auth model follows from the same design and is worth knowing before you connect. Filestack does not accept a stored credential on the wire. It accepts a SIGNED REQUEST: a short policy document naming the operation, the file and an expiry, plus a signature over that policy keyed by your app secret. That is why the credential has two fields rather than one, and why the API key on its own reaches only part of the surface. There is one more consequence worth stating plainly: Filestack documents no endpoint that enumerates an account's files, so no node here can offer you a file picker. A handle is an upload's receipt, and it comes from the node that created the file or from your own records.
One connection, three surfaces
- Visual automations. Drag Filestack nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Filestack node, ready to drop on the canvas
23 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 15
Filestack: Analyze Image Sentiment
Score the emotions on faces in an image across eight categories (HAPPY, SAD, ANGRY, SURPRISED, CONFUSED, CALM, FEAR, DISGUSTED) as percentages that sum to roughly 100. AN IMAGE WITH NO DETECTABLE FACE RETURNS AN EMPTY emotions OBJECT rather than an error, so branch on whether the object is empty before reading a score out of it. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Analyze Text Sentiment
Classify a piece of TEXT as Positive, Negative, Neutral or Mixed, returned as probabilities from 0 to 1. THE ONLY NODE IN THIS CONNECTOR THAT TAKES NO FILE: the text is passed inline, so it pairs naturally with Filestack: Extract Text With OCR to score a scanned document, or with any upstream node that produced text. Note the scores here are 0-to-1 decimals, unlike the 0-to-100 scores tagging returns. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Build Transform URL
Build and SIGN a Filestack CDN URL for a transformation chain, and return it. THIS NODE MAKES NO API CALL: nothing is fetched, nothing is stored, no transformation quota is spent, and the URL is not rendered until somebody opens it. That is what makes it the node most workflows actually want. A transformed image is usually wanted as a LINK - in an email, an img tag, a Slack message, a webhook body - and a link costs nothing to mint. The URL carries a security policy that EXPIRES, so it is a time-limited share rather than a permanent public link. Leave tasks empty to sign a plain delivery URL for the file as stored. If your account has security disabled the URL is still correct, just unsigned.
Filestack: Caption Image
Generate a one-line natural-language description of an image, returned as data.caption. Useful for alt text, for a searchable summary alongside the file, or as the input to a downstream language model. Unlike tagging, this returns prose rather than scored labels. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Check Image Safe For Work
Classify an image as safe for work or not, returning a single boolean in data.sfw. The moderation gate to put in front of anything user-uploaded before it is published or shared. It is a classifier, not a guarantee: treat a false as a definite hold and a true as a probable pass, and keep a human path for appeals. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Detect Document In Image
Find a document inside a photograph - a receipt on a desk, a form held at an angle - and return where it is. With coords on (the default here) you get the bounding rectangle as x, y, width and height, which is what a workflow can branch on. With coords off Filestack instead returns a CORRECTED image of just the document, and the response then carries url, mimetype and size rather than coordinates. THE INPUT IS CAPPED AT 2000 BY 2000 PIXELS: chain a resize in front of it for larger photos, and check the dimensions first with Filestack: Get Image Size. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Detect Faces
Find faces in an image and return one box per face as x, y, width and height in pixels. THE RESPONSE IS A TOP-LEVEL JSON ARRAY, which nothing else in this connector returns, so read it as data[0].x rather than data.faces[0].x, and read its LENGTH to count faces. This node always asks for the exported coordinates rather than the annotated image, because file bytes are never a node output; to actually redact faces, run Filestack: Transform And Store with a blur_faces or pixelate_faces task, or mint a URL for one with Filestack: Build Transform URL.
Filestack: Download File
Read a stored file's CONTENT back into the workflow. Meant for small text assets: a JSON blob, a CSV, a rendered template. THE BODY IS CAPPED AT 256 KB of raw bytes. Content that decodes as UTF-8 comes back as text in `content` with `encoding` set to utf-8; anything else comes back base64 in the same field with `encoding` set to base64. `size` is always the TRUE size and `truncated` says whether you got all of it, so a clipped read is never mistaken for a whole file. For anything larger, or for handing a file to a person or another system, use Filestack: Build Transform URL to mint a signed, time-limited link instead of moving the bytes.
Filestack: Extract Text With OCR
Read printed and handwritten text out of an image or document. Returns the whole extracted text as one string in data.text, plus a hierarchy of text areas, lines and words each with a four-point bounding box, and text_area_percentage saying how much of the image is text. Use data.text for content and the bounding boxes for layout-aware work such as pulling a field out of a form. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Get File Metadata
Read a stored file's metadata without downloading it: size, MIME type, filename, upload time, storage location, container and path, whether it is writeable, and optionally its checksums. Every field is opt-in: ask only for what you need and Filestack returns only that. The cheapest way to confirm a handle still exists. EXIF IS DIFFERENT from every other field here: a security policy allows all calls EXCEPT exif by default, so turning exif on makes this node ask for the exif call explicitly, and that fails on a connection with no app secret.
Filestack: Get Image Size
Return an image's pixel dimensions. The cheapest read in the processing engine, and the one to branch on before deciding how to resize, or before sending an image to Filestack: Detect Document, which rejects anything over 2000 by 2000.
Filestack: Get PDF Info
Read a PDF's structural metadata without converting it: page count, PDF version, creation date, and whether the document is encrypted or password protected. Branch on pages before splitting a document, or on encrypted before sending it to conversion, which fails on protected files.
Filestack: Get Workflow Status
Poll a workflow job and, once it has finished, read its results. status moves from Started to Finished. THE RESULTS ARE KEYED BY TASK NAME PLUS A TIMESTAMP (results.tags_1571950225779.data.tags), so the key is different on every workflow and a consumer must iterate over data.results rather than address a fixed path. ttl is how many seconds the results are retained - 172800, two days, in Filestack's own example - after which polling returns nothing, so collect what you need inside that window. A webhook is the more reliable way to receive results; this node exists for workflows without one. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Tag Image
Describe what is in an image as a set of tags with confidence scores from 0 to 100, under data.tags.auto. data.tags.user is reserved for user-supplied tags and comes back null. Good for auto-categorising an upload, routing it to a folder, or gating a workflow on whether a concept was detected above a threshold. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Transform To JSON
Run a transformation chain whose LAST task returns DATA rather than a file, and return that data. This is the connector's escape hatch onto the whole Processing API: any task Filestack documents is reachable here, including ones with no typed node (video_convert and video_status, pdfcreate, doc_to_images, ascii, and anything Filestack adds later). If the chain returns a FILE rather than JSON, this node says so and tells you to use Filestack: Transform And Store or Filestack: Build Transform URL instead - file bytes are never a node output. Chains that end in imagesize, pdfinfo, ocr, tags, sfw, caption, image_sentiment, doc_detection or detect_faces with export:true all return JSON, and most of those have a typed node of their own with proper config fields.
Action nodes 8
Filestack: Capture Web Page Screenshot
Render a web page and store the screenshot as a file. Wraps Filestack's urlscreenshot task with a store task appended, so the response names the new image (handle = the last path segment of data.url) rather than returning bytes. Useful for archiving a page as evidence, snapshotting a dashboard on a schedule, or building visual diffs. The page must be publicly reachable; a login-gated page renders as whatever an anonymous visitor sees. If your account has a domain whitelist enabled, the target must be on it.
Filestack: Convert File Format
Convert a document or image to another format and store the result: office documents to PDF, PDF pages to images, images between jpg, png and webp. Wraps Filestack's output task and appends a store task, so the response names the NEW file (its handle is the last path segment of data.url) rather than returning bytes. The source is untouched. Converting a multi-page document to an image format returns one page: set page to choose which. Document conversion is the heaviest thing in the processing engine and large files can take a while.
Filestack: Delete File
DESTRUCTIVE and IRREVERSIBLE: delete a file. Filestack has no trash and no versions, so the file, its handle and every URL and embed built on that handle stop working immediately, and nothing can bring any of it back - re-uploading the same bytes produces a DIFFERENT handle, so existing links stay broken. Set skip_storage to remove the file from Filestack while LEAVING the underlying object in your own storage container, which is the only partially recoverable form of this call and only if you configured your own storage. THIS ENDPOINT ALWAYS REQUIRES SECURITY. Filestack documents no response body: success is HTTP 200 with an empty body, so data comes back as {}.
Filestack: Overwrite File
DESTRUCTIVE: replace the CONTENT of an existing file, keeping the same handle. Filestack has no versioning and no trash, so THE PREVIOUS CONTENT IS GONE the moment this succeeds: there is no earlier version to list, no undo, and nothing to restore from. The handle, and therefore every URL and every embed pointing at it, keeps working and silently starts serving the new bytes - which is the whole point of the node and also the reason a wrong handle here is worse than a wrong handle almost anywhere else. Note the CDN caches each unique URL for 30 days, so readers may keep seeing the OLD content until the cache expires or the URL changes. THIS ENDPOINT ALWAYS REQUIRES SECURITY: it fails on a connection with no app secret, regardless of the account's security setting.
Filestack: Run Workflow
Run a Workflow you built in the Filestack Developer Portal against a file. ASYNCHRONOUS: this returns immediately with status Started and a jobid, and the actual results arrive either at your configured webhook or from Filestack: Get Workflow Status. This is also the ONLY way to reach Filestack's Workflows-only intelligence tasks - VIRUS DETECTION and PHISHING DETECTION are not Processing API tasks and have no node of their own, so build a workflow containing them and run it here. Whether the run changes anything depends entirely on what the workflow does: a tagging workflow is a read, a workflow with a store or delete step is not. REQUIRES SECURITY: this fails on a connection with no app secret.
Filestack: Store File From URL
Ingest a file into Filestack by URL. FILESTACK FETCHES THE URL SERVER-SIDE, which is why this is the connector's only upload node: raw file bytes cannot travel through a canvas field, so the source has to be something Filestack can reach. The URL must be publicly readable (or reachable without credentials). The response carries the CDN url, size, MIME type, filename and storage key; THE NEW HANDLE IS THE LAST PATH SEGMENT OF data.url, which every other node in this connector wants. Reversible with Filestack: Delete File.
Filestack: Transform And Store
RUN a transformation chain and PERSIST the result as a new file. This node appends Filestack's store task to whatever chain you give it, so the response is JSON naming the new object rather than the transformed bytes - which is how a transformation is executed without file content ever crossing a node boundary. THE NEW HANDLE IS THE LAST PATH SEGMENT OF data.url. The source file is untouched, so this is reversible by deleting the result. Every run that is not already cached spends transformation quota. Use Filestack: Build Transform URL instead when you only need a link, and Filestack: Transform To JSON when the chain's last task returns data rather than a file.
Filestack: Zip Files
Bundle several files into one zip archive and store it. Wraps Filestack's zip task with a store task appended, so the response names the new archive (handle = the last path segment of data.url). The sources may be Filestack handles or public URLs, mixed freely. Nothing is removed: the originals are untouched and the archive is a new file. Pair it with Filestack: Build Transform URL to hand the archive out as a time-limited download link.
Connecting Filestack takes one credential
Both values come from the Filestack Developer Portal. The API key identifies the app and is public by design: it appears in CDN URLs and in client-side code. The app secret is generated per app under the portal's Security section, is never sent anywhere, and is the HMAC key that signs each request. Regenerating it invalidates every signature already in circulation. Nothing travels in an Authorization header on this connector: the API key is a path segment on the processing host and a query parameter on the File API, and the security material is a base64url policy plus a hex HMAC-SHA256 signature over that policy, minted per call by Mattering with the narrowest set of permissions the node needs and an expiry measured in minutes. Worth checking before you design a workflow around the whole catalog: the API key alone runs the read half of the File API and the unsigned transformation nodes, but it cannot run any Intelligence node, nor overwrite, nor delete, nor read EXIF, all of which Filestack requires security for. Plan matters too. Filestack meters transformations per plan rather than rate limiting them, and documents several tasks as premium or plan restricted, including PDF creation, document-to-images and the enhancement marketplace tasks. Filestack's documentation describes capabilities rather than which plan carries them, so confirm what your plan includes on Filestack's own pricing pages before building a workflow around the Intelligence nodes.
Open the Filestack Developer Portal and copy your app's API key.
In the same portal, open the app's Security section and generate an app secret. Copy it once and store it somewhere you can reach again, because the account holds it and the workflows do not.
In Mattering Automations, open Connectors, click Add Connector, choose Filestack, and create a credential with both values.
Click Test Connection. Mattering signs a small read against Filestack's processing host using a public sample asset Filestack itself documents, which proves the API key is accepted as the URL's first path segment and, on an account with security enabled, that your app secret produces a signature Filestack accepts. Note what a pass does not prove: the File API lives on a different host with a different parameter placement, so run Filestack: Get File Metadata against a real handle once before you trust the store, overwrite and delete half.
All 23 Filestack nodes appear in the canvas palette. Run Filestack: Get Image Size against any public image first: it is the cheapest read in the processing engine and it exercises the same signing path everything else uses.
Common uses for the Filestack MCP
Mint a share link instead of rendering a file
Filestack: Build Transform URL is the highest-value node in the connector and the least obvious one. It signs a transformation chain and returns the URL, and it makes NO network call: nothing is fetched, nothing is stored, and no transformation quota is spent. What a workflow usually wants from a transformation is a link to drop into an email, an image tag, a Slack message or a webhook body, and minting one costs nothing. Because the URL carries an expiring policy, it is a time-limited share rather than a permanent public link, and the expiry is a field on the node. When you do need the result to persist, Filestack: Transform And Store is the node that runs the same chain and answers with JSON naming the new file.
Moderate and describe every user upload before a person sees it
The eight Intelligence nodes are the part of Filestack that agents reach for most. Filestack: Check Image Safe For Work returns a single boolean, which is the moderation gate to put in front of anything user-supplied before it is published. Filestack: Tag Image describes what is in the picture with confidence scores, Filestack: Caption Image writes a one-line description that doubles as alt text, and Filestack: Extract Text With OCR reads printed and handwritten text out of an image or a document. All four are reads, so they are comfortable to hand to an agent. Two shapes to know: tag confidences come back on a 0 to 100 scale while text sentiment comes back as probabilities from 0 to 1, and Filestack: Analyze Image Sentiment returns an empty emotions object rather than an error when no face is detected, so branch on emptiness before reading a score out of it.
Ingest by URL, then keep the handle where you can find it again
Filestack: Store File From URL is the connector's only ingestion node, and that is a deliberate shape rather than a gap: Filestack fetches the URL server-side, so no file bytes ever travel through a canvas field. The important habit is what you do with the response. The File API returns no handle field of its own; the handle is the last path segment of data.url, and since Filestack documents no endpoint that lists an account's files, nothing can look it up for you later. Write it into a Mattering database row or onto the task or record the file belongs to, in the same run that created it.
Convert, screenshot and bundle without learning the grammar
Five typed chains give real config fields to the transformations people reach for most often. Filestack: Convert File Format takes office documents to PDF, PDF pages to images, and images between jpg, png and webp. Filestack: Capture Web Page Screenshot renders a page and stores the image, which is a genuinely useful scheduled job for anything you want a visual record of. Filestack: Zip Files bundles several files into one archive. Filestack: Get Image Size and Filestack: Get PDF Info are the cheap reads to branch on first: check the pixel dimensions before deciding how to resize, or the page count before splitting a document. Each of these appends Filestack's own store task, so the response names the new file rather than returning bytes.
Run a Developer Portal Workflow and collect what it found
Filestack: Run Workflow triggers a Workflow you built in the Developer Portal against a file, and Filestack: Get Workflow Status polls it and returns the results. This is also the supported route to two capabilities that have no Processing API node, because Filestack documents them as Workflows-only: virus detection and phishing detection. Two facts govern how you read the output. The results are keyed by task name plus a timestamp, so the key differs on every run and a consumer has to iterate data.results rather than address a fixed path. And workflow results expire on a TTL, so collect them inside the window rather than assuming they will still be there tomorrow. The node is classed as an action rather than a read because what a run DOES is whatever the workflow contains: a tagging workflow reads, a workflow with a store or a delete step does not.
Example: Screen an inbound upload, publish what passes, and keep the receipt
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a form submission or an inbound webhook arrives carrying a publicly reachable file URL.
Filestack: Store File From URL ingests it. The workflow immediately reads the handle out of data.url's last path segment and writes it into a Mattering database row, because nothing in Filestack's API can look that handle up again later.
Filestack: Check Image Safe For Work runs on the new file. A condition branches on data.sfw: anything that fails opens a task for a human and the run stops there.
Filestack: Tag Image and Filestack: Caption Image run in parallel on what passed. The tags and the one-line description land on the same database row, which is what makes the file findable later given that Filestack itself has no search.
Filestack: Transform And Store runs a resize and compress chain to produce the thumbnail the site will actually serve, and Filestack: Build Transform URL mints a short-lived signed link to the full-size original for the review email. The second of those costs no transformation quota, because it renders nothing.
A notification node posts the caption, the tags and the two links into the channel that reviews new uploads.
Filestack MCP questions, answered
What Filestack operations are supported?
23 nodes: 15 reads and 8 actions. On the File API, read metadata, download a small file (capped at 256 KB of raw bytes), ingest a file from a URL, overwrite a file's content and delete a file. On the transformation grammar, build and sign a transformation URL without making a call, run a chain and store the result, and run a chain whose last task answers with JSON. Five typed chains cover format conversion, web page screenshots, zipping, image dimensions and PDF structure. Eight Intelligence nodes cover OCR, image tagging, safe-for-work classification, captioning, image sentiment, text sentiment, document detection and face detection. Two Workflows nodes run a portal Workflow and poll its results. Deliberately not included: the multipart upload API (it exists to stream local bytes from a browser or SDK, and ingestion by URL covers the server-side case), the asynchronous video and audio processing surface, the File Picker browser widget, and webhook management, for which Filestack documents no endpoints.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Why is there no node for every Filestack transformation?
Because Filestack's transformations are not endpoints. The Processing API is one URL grammar of roughly seventy named tasks written into the path, and the tasks COMPOSE: resize then compress then output is a single request that renders a single result. Shipping seventy nodes would misrepresent the shape of the API and would also be unusable, because a one-task-per-node palette cannot express a chain. You would wire N nodes in series, each making its own billed round trip, to get what Filestack renders in one. So the connector splits the grammar by what comes back rather than by task name: a node that signs a URL and calls nothing, a node that runs a chain and stores the result, and a node that runs a chain answering with JSON. Any task Filestack documents, including the ones with no dedicated node here, is reachable through those three with full parameter fidelity, and the five typed chains plus eight Intelligence nodes give real config fields to the ones people reach for by name.
Filestack publishes an official Claude plugin exposing MCP tools. Why use this connector?
It does, and for some jobs a vendor server is the better answer. If what you want is an assistant that helps you work with Filestack itself in your own editor or client config, use Filestack's server. This connector is shaped for operations instead: the same 23 nodes run as steps on an automation canvas AND over MCP, so a file check can run on a schedule or off a trigger with nobody present, chain in the same workflow with every other connector in the catalog, hold the credential once in a shared workspace store rather than in each person's local config, and carry destructive flags you can gate on. Neither replaces the other, and nothing here disparages Filestack's own tooling.
Why does the credential need an app secret as well as an API key?
Because Filestack authenticates a REQUEST rather than a caller. Every protected call carries a small policy document naming the operation, usually the specific file, and an expiry, plus a signature over that policy keyed by your app secret. The API key is public by design, since it appears in CDN URLs, so on its own it cannot prove anything. Mattering mints the policy and signature per call, with the narrowest set of permissions the node needs and a short expiry, so a leaked URL leaks one file for a few minutes rather than the account. In practice this means the API key alone runs the read half of the File API and the unsigned transformation nodes, and cannot run any Intelligence node, nor overwrite, nor delete, nor read EXIF. Those nodes fail with a message naming the missing field rather than a confusing 403.
Can an AI agent delete my files by accident?
Two nodes are flagged destructive so you can gate them: Filestack: Delete File and Filestack: Overwrite File. Neither has an undo, because Filestack keeps no versions and no trash. Delete takes the file, its handle and every URL built on that handle immediately, and re-uploading the same bytes mints a DIFFERENT handle, so existing links stay broken. Overwrite is the subtler one: the handle survives while the content behind it changes, so every page and embed pointing at it silently starts serving the new bytes, and the previous content is unrecoverable. The honest guardrails are structural: keep agents on the read nodes and the ingest node, put both destructive nodes behind a condition or an approval task, and note that the credential's app secret is what makes them reachable at all, so a connection with only the API key cannot run either one.
Is there a file picker, and how do I get a handle?
There is no picker, and that is a fact about Filestack rather than a missing feature here. Filestack documents no endpoint that enumerates an account's files: no list, no search, no browse, no recent uploads. The File API is five endpoints, four of which are addressed BY a handle you already hold and the fifth of which mints one. So a handle comes from an upstream node's output, and specifically from the last path segment of data.url, because the File API returns no handle field of its own. The practical habit is to store the handle in the same run that created the file, on the record the file belongs to. Every node that takes a handle says where it comes from in its own description.
Are the Intelligence tasks available on any plan?
Filestack's documentation describes what each task does rather than which plan carries it, and the pricing pages are maintained separately, so the honest answer is to check your own plan rather than take a number from us. What can be stated: the app secret is required for overwrite, delete and EXIF metadata, which Filestack documents as always needing a policy and signature, and for every processing request including the Intelligence tasks once your application has security enabled in the Developer Portal. Because most production Filestack applications run with security on, treat the app secret as required rather than optional. Filestack meters transformations per plan rather than publishing a numeric request rate limit for these surfaces, and documents several tasks as premium or plan restricted, including PDF creation, document-to-images and the enhancement marketplace tasks. Video and audio processing is a paid add-on rather than a plan tier, and is not built as nodes here. The grammar nodes surface Filestack's own error rather than pre-judging your plan, so if a task is not included you get Filestack's message rather than a guess from Mattering.
Why did an overwritten file keep serving the old version?
That is the CDN cache, and Filestack documents it: each unique transformation URL is cached for up to 30 days before it is re-fetched. So after Filestack: Overwrite File succeeds, anyone holding a cached URL can keep receiving the previous bytes for as long as that entry lives, which makes overwrite look like it did nothing. The same caching works in your favour elsewhere, because a repeated identical transformation URL is served from cache rather than re-rendered and re-metered. One consequence worth planning around: a signed URL whose policy has expired is a DIFFERENT URL, so re-signing misses the cache and re-renders. If a workflow mints links on a schedule, widen the expiry on the node rather than re-signing the same transformation more often than you need to.
Put Filestack to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Filestack is a product of its respective owner; Mattering is an independent platform.