Send attached files for extraction when new issues are filed
When a new issue is captured in GitHub, send attached system logs or documents to Sensible for structured extraction.
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.
Sensible Explore Sensible →
TriggersFires when Sensible finishes extracting data from a document.
Posts a file to Sensible to be parsed.
Runs an extraction template in Sensible against a document.
GitHub Explore GitHub →
TriggersFires when a new error or issue is captured in GitHub.
Fires when an issue's status changes in GitHub.
Fires when a new deployment is tracked in GitHub.
Creates or updates an issue in GitHub.
Assigns an issue in GitHub to a teammate.
Resolves or mutes an issue in GitHub.
More Sensible + GitHub workflows
See all Sensible + GitHub integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Send attached files for extraction when new issues are filed” between Sensible and GitHub?
Yes — describe it in the box above and Knit's Integrations Agent researches Sensible and GitHub'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.
How do dev teams benefit from connecting Sensible and GitHub?
Technical teams can turn extracted document insights or failed processing data straight into bug reports and trackable engineering tasks in GitHub.
Can filing a bug automatically initiate document parsing?
Yes, creating a new issue in GitHub can automatically send attached log files or PDF reports to Sensible for automated data extraction.