Uploadcare integration

What it does

The Uploadcare integration lets your agency run a client's file pipeline from any workflow. Connect a client's Uploadcare project once and your workflows can upload files (from an earlier step or from a URL), read and store them, tag them with metadata, bundle them into groups, run Uploadcare's add-ons (background removal, virus scanning, image labeling, moderation), convert documents and encode video. Triggers fire the moment a file is uploaded, stored, deleted, or has its metadata or add-on results updated.

Connect an Uploadcare account

1. In TaskJuice, add an Uploadcare node to a workflow and choose to create a connection from it.
2. In a new tab, sign in to app.uploadcare.com and open the client's project.
3. Open the project's API keys tab and copy the public key and the secret key.
4. Paste them into TaskJuice as public_key:secret_key (a colon between, no spaces).
5. Paste the public key on its own into Public key. Upload File, Upload File from URL and Create File Group need it, because Uploadcare's Upload API identifies the project by public key only.

To rotate the keys later, regenerate the secret in the project's API keys tab and update the connection. Use a separate Uploadcare project per client so revoking one client's access never touches another.

Triggers

• File Uploaded fires when a new file lands in the project, with its UUID, file name, MIME type, size and CDN URL.
• File Stored fires when a file is marked as stored and kept past Uploadcare's 24-hour window.
• File Deleted fires when a file is removed from the project.
• File Info Updated fires when a file's metadata or add-on results change, for example when a virus scan, label detection or background removal finishes. The payload carries the previous values beside the new ones.

TaskJuice registers the Uploadcare webhooks for you when you publish a workflow with one of these triggers, signs them with a secret it generates, and verifies every delivery's X-Uc-Signature header before running the workflow.

Actions

Files

• Upload File uploads a file from an earlier step (an email attachment, a download, a form upload), up to 100 MB.
• Upload File from URL has Uploadcare fetch a file from a public URL. Large files return a token; pass it to Get URL Upload Status.
• List Files pages through the project's files, with stored and removed filters.
• Get File reads one file's details, CDN URLs and image information.
• Store File keeps an upload permanently instead of for 24 hours.
• Copy File creates a new file from an existing one or from a CDN URL with processing operations, such as a resized image.
• Delete File deletes a file so it stops being served from the CDN.

Metadata

• Get File Metadata reads every metadata key on a file.
• Set File Metadata creates or overwrites one key, such as a client ID or job reference.
• Delete File Metadata removes one key.

Groups

• Create File Group bundles up to 25 files into one group with a shared CDN URL.
• List Groups, Get Group and Delete Group manage existing groups. Deleting a group keeps its files.

Add-ons

• Remove Background cuts out the subject of an image into a new file.
• Scan File for Viruses runs a ClamAV scan, and can delete the file if it is infected.
• Detect Image Labels and Detect Moderation Labels tag an image with what it shows, or flag unsafe content.
• Get Add-on Status checks a run started by any of the four add-ons above. Results land in the file's details and fire File Info Updated.

Conversion

• Convert Document converts a document to another format, such as DOCX to PDF, or pages to images.
• Convert Video encodes a video to MP4, WebM or Ogg at a chosen quality.
• Get Document Conversion Status and Get Video Conversion Status check a conversion by its token.

Project

• Get Project reads the project's name, public key and autostore setting.

Known limitations

• Webhooks are a paid Uploadcare feature. On the free plan the triggers cannot be registered, and publishing reports the provider's refusal.
• Add-ons, document conversion and video encoding are billed by Uploadcare per use. Check the client's plan before running them in a loop.
• A connection made before the Public key field existed still runs every other action, but Upload File, Upload File from URL and Create File Group need you to reconnect and add the public key.
• Upload File accepts up to 100 MB per request. Larger files need Uploadcare's multipart upload, which TaskJuice does not run.
• Projects with signed uploads turned on reject Upload File, Upload File from URL and Create File Group, because those calls carry no upload signature. Turn signed uploads off for the project, or use Copy File from an existing file.
• Uploadcare limits request rates per project. A 429 response is retried automatically; 401 and 403 responses mean the keys are wrong or revoked.