Archive build files when a deployment is logged
When a new deployment is tracked in CloudConvert, automatically upload the build report and release artifacts to Pic-Time.
See all Pic-Time + CloudConvert integrations or talk to a human
Opens Claude with Knit filled in: click Continue. Claude web and desktop share one connector list. Or paste this link in Settings > Connectors > Add custom connector.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents claude
Run in your own terminal, then restart Claude Code. Adds the server, the Knit skill and a CLAUDE.md note.
Turn on developer mode, then create a connector named Knit with this link and No Auth.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents codex
Run in your own terminal (not through Codex), then start a new Codex session.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents antigravity
Run in your own terminal, then reload MCP servers (/mcp in the CLI, refresh in the IDE).
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents cursor
Run in your own terminal, restart Cursor, then paste the note it prints into User Rules.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Pic-Time Explore Pic-Time →
TriggersFires when a new file is uploaded to Pic-Time.
Fires when a file in Pic-Time is shared with someone new.
Fires when a folder's contents change in Pic-Time.
Uploads a file to Pic-Time.
Creates a new folder in Pic-Time.
Shares a file from Pic-Time with a link or user.
CloudConvert Explore CloudConvert →
TriggersFires when a job, build or file conversion finishes in CloudConvert.
Fires when a job, build or API request fails in CloudConvert.
Calls an CloudConvert endpoint with data from an earlier step.
Creates a PDF, image or converted file with CloudConvert.
Checks or enriches a phone number, address or IP with CloudConvert.
More Pic-Time + CloudConvert workflows
See all Pic-Time + CloudConvert integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Archive build files when a deployment is logged” between Pic-Time and CloudConvert?
Yes — describe it in the box above and Knit's Integrations Agent researches Pic-Time and CloudConvert's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why integrate CloudConvert with Pic-Time?
Connecting these apps ensures that logs, design specs, and build artifacts uploaded to Pic-Time instantly generate tracking items in CloudConvert.
Can deployment reports from CloudConvert be archived automatically in Pic-Time?
Yes, whenever a new deployment is tracked in CloudConvert, documentation can be saved and shared directly within Pic-Time.