Connect Parliament Bills and setlist.fm
Describe what you want to happen between Parliament Bills and setlist.fm 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.
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
setlist.fm
15 documented operations. See all setlist.fm operations
- GETGet a complete list of all supported countries
/1.0/search/countries - GETSearch for a city
/1.0/search/cities - GETSearch for venues
/1.0/search/venues - GETSearch for artists
/1.0/search/artists - GETSearch for setlists
/1.0/search/setlists - GETGet a user by userId
/1.0/user/{userId}
How a Parliament Bills and setlist.fm 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 Parliament Bills and setlist.fm, 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
- OData for namespace microsoft.graph and Parliament Bills11,431 operations
- OData for namespace microsoft.graph and setlist.fm11,427 operations
- Cloudflare and Parliament Bills3,141 operations
- Cloudflare and setlist.fm3,137 operations
- NetBox and Parliament Bills863 operations
- NetBox and setlist.fm859 operations
- GitHub and Parliament Bills830 operations
- GitHub and setlist.fm826 operations
- Mist and Parliament Bills787 operations
- Mist and setlist.fm783 operations
Questions about connecting Parliament Bills and setlist.fm
- Can Parliament Bills connect with setlist.fm?
- 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 Parliament Bills to setlist.fm?
- 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 Parliament Bills and setlist.fm?
- 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 Parliament Bills and setlist.fm?
- Parliament Bills publishes 19 documented operations and setlist.fm publishes 15. 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 Parliament Bills or setlist.fm is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Parliament Bills and setlist.fm. Descriptions are each provider’s own words, not ours.