Integration
Connect Customer.guru to Data.parliament.uk
When something happens in Customer.guru, your agent does the next thing in Data.parliament.uk. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Customer.guru and Data.parliament.uk to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Customer.guru and Data.parliament.uk
Triggers and actions 1 trigger · 7 actions
Trigger
New RatingTriggered when a customer submits a new rating on one of your Customer.guru surveys, giving you their score, their comment and how they engaged with the survey email.
Action
Find CustomerLooks up a customer in your Customer.guru account by email address and returns that customer's record — their id, when they were added, their most recent survey score and comment, and whether they have unsubscribed.
Action
Schedule SurveySends a Customer.guru NPS survey to one or more customers, either straight away or scheduled for a later date, and reports how many went out.
Action
Find billsSearch UK Parliament bills by title, session, or status, with paging via data.parliament.uk's common query-string options. Endpoint: GET /bills.
Action
Find divisionsSearch UK Parliament voting divisions (Commons/Lords) by date range or title, with paging. Endpoint: GET /divisions.
Action
Find early day motionsSearch UK Parliament early day motions (EDMs) by title, member, or date, with paging via data.parliament.uk's common query-string options. Endpoint: GET /edms.
Action
Find membersSearch UK Parliament members (MPs and Lords) by name, party, constituency, gender, or other biography fields, with paging. Endpoint: GET /members with query-string filters (e.g. family-name=, party=), _pageSize, _page, _sort, _search per data.parliament.uk's common query options.
Action
Get memberRetrieve full biography details for a single UK Parliament member by their data.parliament.uk record id. Endpoint: GET /members/{id}.json.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.