Log deploys in an internal app
When a release or deploy completes in PDF-API.io, create a record in Glide.
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.
PDF-API.io Explore PDF-API.io →
TriggersFires when a job, build or file conversion finishes in PDF-API.io.
Fires when a job, build or API request fails in PDF-API.io.
Calls an PDF-API.io endpoint with data from an earlier step.
Creates a PDF, image or converted file with PDF-API.io.
Checks or enriches a phone number, address or IP with PDF-API.io.
Glide Explore Glide →
TriggersFires when a new record is added to an app built in Glide.
Fires when a record changes in an Glide app.
Fires when a record is deleted in an Glide app.
Adds a new record to an app built in Glide.
Updates an existing record in an Glide app.
Removes a record from an Glide app.
More PDF-API.io + Glide workflows
See all PDF-API.io + Glide integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Log deploys in an internal app” between PDF-API.io and Glide?
Yes — describe it in the box above and Knit's Integrations Agent researches PDF-API.io and Glide'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.
Can a record in Glide create an issue in PDF-API.io?
Yes. When a record such as a bug report or request is created in Glide, PDF-API.io can open an issue or run a workflow.
Can developer events update my app?
When an issue closes or a deploy finishes in PDF-API.io, the related record in Glide can be updated automatically.