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