Img2Go
Utilities & PersonalConvert files with Img2Go on QaamGo's shared API2Convert REST API, covering image, document, and media formats. Agents normalize whatever arrives into the format the next system will accept.
What This Integration Enables
Img2Go is one of QaamGo's file-conversion brands, and it runs on their shared API2Convert REST API alongside online-convert.com, pdf2go.com, and ocr2edit.com. That fact is worth stating plainly, because it explains both the family resemblance and the reach. The image-specific operations are the front door, but Convert File reaches every category the shared API supports: video, audio, document, ebook, archive, CAD, hash, and metadata targets. List Conversion Targets returns the full option schema for each one, with option names, types, defaults, and permitted values, which is the authoritative way to discover what a given conversion accepts rather than guessing at parameter names.
What distinguishes this connector from a converter is that it exposes the job object rather than hiding it. A job has inputs you can add and remove, outputs you can list and delete, a status history you can read, and a lifecycle you can interrupt. Add Input From URL batches several files through one job. Cancel Job stops a runaway conversion and frees the credits it would have burned. Delete Job Output removes a converted file from the vendor's side as soon as it has been copied into your own storage, rather than waiting out the 24 hour retention window. Wait For Job Completion collapses the whole submit-and-poll pattern into one blocking step when a flow reads better that way. This is what a mature connector looks like: the convenience path is there, and the control the convenience path hides is still reachable when a workflow needs it.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Building the derivative set for a product launch
Source photography lands in Amazon S3. For each asset the agent starts a Convert Image From File job for the primary web format, a Resize Image job for each listing and thumbnail size the storefront needs, and a Compress Image job targeting the absolute byte ceiling the email template allows. Wait For Job Completion holds each one until it reaches completed, failed, or invalid, with the timeout raised for large sources. Download Output File copies every result into FlowRunner file storage, which is what makes the assets usable later, because the vendor deletes processed files after 24 hours. The finished URLs are written back to the product record and published through WordPress.
Batching several files through one job
A partner supplies a folder of mixed assets for a campaign. Rather than one job per file, the agent creates a job with processing disabled, calls Add Input From URL for each source, and uses List Job Inputs to confirm every input downloaded successfully, with its resolved filename, byte size, and checksum. Inputs that failed to download are dropped with Delete Job Input rather than discarding the whole job. Start Job then releases the batch. Get Job History afterwards shows how the status progressed and when each transition occurred, which is how a failed batch gets diagnosed without rerunning it.
Watching the credit balance before a big run
Before dispatching a large batch, the agent calls Get Account Contracts to read the plan in force and the conversion allowance attached to it, and Get Monthly Usage Statistics for the month to date broken down by the chosen filter. If the remaining capacity will not cover the run, the batch is held and the shortfall is reported rather than half-completed. The same two actions run on a schedule to charge conversions back to the teams generating them and to catch a runaway integration before the balance is gone.
Human-in-Loop Highlight
The gate on this connector is metadata stripping, and it is interesting precisely because both answers are wrong somewhere. Publishing a customer-submitted photograph with its EXIF intact can expose the GPS coordinates of the place it was taken, which for a photograph of a home, a vehicle, or a person is a disclosure nobody consented to and which cannot be recalled once the image has been indexed. That argues for stripping by default. But metadata is also evidence. On an insurance claim photograph, a field inspection record, or a warranty dispute, the capture timestamp and the coordinates are the entire reason the image was collected, and a stripped copy is worth nothing if the claim is later contested.
An agent cannot tell those two cases apart from the file. It can tell you which files carry something. So it does that, and stops: "9 of 40 submitted images carry embedded metadata. 6 include GPS coordinates, 3 include device serial numbers. The other 31 carry nothing. Strip all 9 before publication, preserve the 6 with coordinates as claim evidence and strip the rest, or hold the batch?" The content owner answers with the context that lives outside the file, what these images are for. Then the agent configures the jobs accordingly and runs the batch. This is what FlowRunner means by agents that know when to stop and ask: not a checkpoint bolted onto every step, but a pause at the one place where the same operation is correct in one context and a disclosure in another. Human-in-the-loop is a default you get, not a tax you pay.
Agent Capabilities
21 actionsImage Conversion
4- Convert Image From URL Starts a job that downloads a publicly reachable image and converts it to another format, optionally resizing, rotating, mirroring, recolouring, and recompressing it in the same pass. Returns a job with an id and token that must be polled before the result can be fetched.
- Convert Image From File Converts an image held in FlowRunner file storage by running the documented upload flow: the job is created unprocessed, the bytes are posted to its input collection, and the job is then started. Supports the same options as the URL variant, without exposing the file publicly.
- Resize Image Starts a dedicated resize job that scales an image to a target width, height, or aspect ratio without a full format conversion, though the output container can still be chosen. Sizes may be given in pixels, percent, inches, centimetres, or millimetres.
- Compress Image Starts a job that reduces file size by a named compression level, by targeting an absolute size in bytes, or by targeting a percentage of the original. Metadata can be stripped at the same time to shrink the file further.
Conversion Beyond Images
2- Convert File Starts a conversion for any category the shared API supports, including video, audio, document, ebook, archive, CAD, hash, and metadata targets. Use List Conversion Targets to discover the valid target identifiers and their options for a category.
- List Conversion Targets Returns every conversion the API supports, optionally filtered to one category and target, with the full option schema for each: option names, types, defaults, and permitted values. This is the authoritative source for what can be passed to Convert File or to Advanced Options.
Job Lifecycle
7- Get Job Retrieves the current state of a job including its status code, errors and warnings, configured conversions, inputs, and, once processing completes, its output files with download URIs. This is the endpoint to poll while a conversion runs.
- Wait For Job Completion Polls a job until it reaches completed, failed, or invalid, or until the timeout expires, then returns the final job record with its output files. Turns the submit-and-poll model into one blocking step. Raise the timeout for large videos and long documents.
- Start Job Marks a job that was created but not yet processed as ready to run. Used when a job was created with processing disabled so inputs or extra conversions could be attached first.
- Cancel Job Cancels a job before it starts or while it is being processed. Used to abandon runaway conversions and to free credits that would otherwise be spent on inputs that turned out to be wrong.
- List Jobs Lists the jobs belonging to the API key, optionally narrowed to a single status, paginated at 50 per page. Used for dashboards, cleanup routines, and finding jobs started earlier in a flow.
- Get Job History Returns the recorded change history for a job, showing how its status progressed and when each transition occurred. Used to diagnose a failure and to measure how long each stage of a pipeline takes.
- List Job Statuses Returns the full set of status codes the API can report with a human-readable explanation for each. Used to interpret Get Job and to build status handling that stays correct if the vendor adds codes.
Job Inputs
3- Add Input From URL Attaches an additional source file to an existing job by URL. Used to batch several files through one job or to build a job incrementally before starting it. A download engine can be selected so web pages, embedded videos, or screenshots are captured rather than the raw response.
- List Job Inputs Lists the source files attached to a job with each one's download status, resolved filename, byte size, and checksum. Used to confirm every input downloaded before starting a job, and to diagnose a job that failed at the input stage.
- Delete Job Input Removes a single source file from a job before processing. Used to drop an input that failed to download or was attached in error without discarding the whole job.
Job Outputs
3- List Job Outputs Lists the converted files a completed job produced, with filename, download URI, byte size, MIME type, checksum, and download counter. Called after the job reaches completed to discover what to download.
- Download Output File Fetches a converted file and stores it in FlowRunner file storage, returning a durable URL. The vendor deletes processed files after 24 hours, so copying them into storage is what makes a result usable later in a flow. When no output is named the first output of the job is taken.
- Delete Job Output Deletes a converted file from a job's output collection so it can no longer be downloaded. Used to remove sensitive results as soon as they have been copied into your own storage rather than waiting out the 24 hour retention window.
Account
2- Get Account Contracts Returns the active contracts on the account, describing the plan in force and the conversion allowance attached to it. Used to check remaining capacity before dispatching a large batch.
- Get Monthly Usage Statistics Returns aggregated usage for a calendar month broken down by the chosen filter. Used for cost monitoring, for charging conversions back to teams, and to spot a runaway integration before the balance is exhausted.
Frequently Asked Questions
What can FlowRunner do with Img2Go?
FlowRunner agents can run Convert Image From URL, Convert Image From File, and Resize Image in Img2Go, plus 18 more actions.
Does connecting Img2Go to FlowRunner require OAuth?
No. Img2Go connects to FlowRunner with an API key, no OAuth flow required.
Can Img2Go trigger a FlowRunner workflow automatically?
Img2Go doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Img2Go
$100 in credits. No card required. Connect in minutes.