Filestack
StorageHandle file ingestion and processing through Filestack. Agents store files from URLs, read metadata, build transformation URLs for resizing and conversion, run tag detection, and delete assets when they expire.
What This Integration Enables
Filestack collapses the entire media pipeline, ingest, storage, transformation, delivery, into API calls and URLs, which makes it a natural set of hands for an agent. FlowRunner agents pull files in from wherever they appear, validate what actually arrived, classify images with AI tagging, and mint the exact CDN URLs each downstream surface needs. Because transformation URLs are assembled without an API call, an agent can generate every variant a storefront or app requires in a single pass. - Ingest images and documents from public URLs into managed storage, no byte-shuffling - Generate thumbnails, WebP conversions, and cropped previews as on-demand CDN URLs - Produce direct or force-download links, including for private, security-protected files - Auto-categorize and moderate uploads with detected tags and confidence scores - Validate ingests by size, MIME type, checksum, and storage location - Retire expired assets with a governed, human-approved cleanup For security-enabled apps, the connector carries your Security Policy and Signature through automatically, embedding them in the CDN URLs it builds and applying them to the API calls that require them. That means private files stay private without agents handling raw credentials in workflow logic, and the operations Filestack gates behind delete permission stay gated. That last item is where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline earns its keep, because Filestack deletion is genuinely permanent. Everything else in this connector is cheap to redo; the delete is the one call that is not.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Product images that arrive production-ready
A [Shopify](/integrations/shopify) product goes live with a raw supplier image. The agent calls Store File from URL to bring it into managed storage, validates the result with Get File Metadata, then assembles Build Transformation URL variants: a 400-pixel cropped thumbnail, a WebP conversion for page weight, a sharpened hero crop. The URLs go back onto the product record. The CDN renders each variant on first request, and no engineer wrote a resize job or will ever maintain one.
Upload moderation with a paper trail
User-submitted images flow into the platform all day. For each new handle, the agent runs Detect Tags and logs the handle, tags, and confidence scores to [Google Sheets](/integrations/google-sheets). Images whose tags clash with policy or with their declared category go to a moderator in [Slack](/integrations/slack) with the content URL attached and the confidence scores that triggered the flag. Clean images pass through untouched. The moderation queue contains only the files worth a human's attention, and the sheet shows why every decision, human or automated, went the way it did.
Private files shared on purpose
A report lives as a private object in [Amazon S3](/integrations/aws-s3). The agent exposes it briefly with a presigned URL, ingests it via Store File from URL into a security-enabled Filestack app, and mints a policy-signed link with Get Content URL, optionally forcing download with a clean filename. The link posts to the requesting team's channel. Access rides on the Filestack Security Policy rather than on an S3 bucket someone quietly made public and forgot.
Human-in-Loop Highlight
Delete File permanently removes a stored file from Filestack and its underlying storage, and the platform requires security credentials with delete permission precisely because there is no undo. The dangerous moment is the storage cleanup sweep: an agent reasons that a handle has not been referenced in ninety days, deletes it, and a customer-facing page somewhere renders a broken image forever. So FlowRunner cleanup workflows never let the agent hold the trigger. The agent assembles the case per file, handle, filename, upload date, last known references, the Get File Metadata record, and posts the deletion batch for review. A person scans the list, pulls out anything that looks load-bearing, and approves the rest. The agent then deletes at machine speed and logs every handle it destroyed. Storage stays lean, and nothing irreplaceable dies to a heuristic.
Agent Capabilities
6 actionsFile Management
4- Store File from URL Fetches a file from a public URL server-side and stores it in Filestack's S3-backed storage, returning the URL, handle, size, MIME type, and filename. The handle is the identifier every other operation uses.
- Get File Metadata Retrieves a stored file's size, MIME type, filename, upload timestamp, and writeable flag, with optional storage location, source URL, and MD5 checksum. The validation step after every ingest.
- Get Content URL Builds the CDN content URL for a handle without an API call, optionally forcing download with a custom filename. Embeds the Security Policy and Signature so protected files stay accessible.
- Delete File Permanently deletes a stored file and its underlying storage object by handle. Irreversible, and the operation this page's human gate exists for.
Transformations
1- Build Transformation URL Assembles an image transformation URL from a handle or source URL, chaining tasks like resize, crop, rotate, format conversion, compress, sharpen, and blur in Filestack task syntax. The CDN applies them on demand.
AI
1- Detect Tags Runs AI image tagging on a stored image, returning detected objects, scenes, and concepts with confidence scores. The classification step behind auto-labeling and moderation flows.
Frequently Asked Questions
What can FlowRunner do with Filestack?
FlowRunner agents can run Store File from URL, Get File Metadata, and Get Content URL in Filestack, plus 3 more actions.
Does connecting Filestack to FlowRunner require OAuth?
No. Filestack connects to FlowRunner with an API key, no OAuth flow required.
Can Filestack trigger a FlowRunner workflow automatically?
Filestack doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Filestack
$100 in credits. No card required. Connect in minutes.