Connect CircleCI and Parliament Bills
Describe what you want to happen between CircleCI and Parliament Bills in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
CircleCI
22 documented operations. See all CircleCI operations
- POSTAdds your Heroku API key to CircleCI
/user/heroku-key - POSTCreates a new environment variable
/project/{username}/{project}/envvar - POSTCreates a new checkout key
/project/{username}/{project}/checkout-key - POSTTriggers a new build, returns a summary of the build
/project/{username}/{project} - POSTCreate an ssh key used to access external systems
/project/{username}/{project}/ssh-key - POSTTriggers a new build, returns a summary of the build
/project/{username}/{project}/tree/{branch}
Parliament Bills
19 documented operations. See all Parliament Bills operations
- GETReturns a list of Bills
/api/v1/Bills - GETReturns a list of Bill stages
/api/v1/Stages - GETReturns a list of Sittings
/api/v1/Sittings - GETReturns a list of Bill types
/api/v1/BillTypes - GETReturns a list of publication types
/api/v1/PublicationTypes - GETReturns a list of news articles for a Bill
/api/v1/Bills/{billId}/NewsArticles
How a CircleCI and Parliament Bills automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in CircleCI and Parliament Bills, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- CircleCI and OData for namespace microsoft.graph11,434 operations
- OData for namespace microsoft.graph and Parliament Bills11,431 operations
- CircleCI and Cloudflare3,144 operations
- Cloudflare and Parliament Bills3,141 operations
- CircleCI and NetBox866 operations
- NetBox and Parliament Bills863 operations
- CircleCI and GitHub833 operations
- GitHub and Parliament Bills830 operations
- CircleCI and Mist790 operations
- Mist and Parliament Bills787 operations
Questions about connecting CircleCI and Parliament Bills
- Can CircleCI connect with Parliament Bills?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect CircleCI to Parliament Bills?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate CircleCI and Parliament Bills?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across CircleCI and Parliament Bills?
- CircleCI publishes 22 documented operations and Parliament Bills publishes 19. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either CircleCI or Parliament Bills is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for CircleCI and Parliament Bills. Descriptions are each provider’s own words, not ours.