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