Integration
Connect Conversion Tools to Represent by Open North
When something happens in Conversion Tools, your agent does the next thing in Represent by Open North. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Conversion Tools and Represent by Open North 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 Conversion Tools and Represent by Open North
Triggers and actions 4 triggers · 9 actions
Trigger
Conversion FailedTriggered when a file conversion fails, giving the reason it failed.
Trigger
Conversion Result AvailableTriggered when a finished conversion has its result file ready to download.
Trigger
Conversion StartedTriggered when a new file conversion is submitted, while it is still queued or running.
Trigger
Conversion Successfully FinishedTriggered when a file conversion finishes successfully.
Action
Convert FileUploads a file to Conversion Tools and starts converting it, returning the conversion ID. Use one of the result triggers or Convert File and Get the Result to pick up the converted file.
Action
Convert File and Get the ResultUploads a file to Conversion Tools, converts it, waits for the conversion to finish and returns a link to download the result.
Action
Find representatives by pointFind elected officials for a given latitude/longitude. GET /representatives/?point={lat},{lng} (optionally scoped to a representative set via /representatives/{set}/?point=...); supports filters like last_name, party_name, elected_office.
Action
Find representatives by postal codeLook up elected officials and boundaries covering a Canadian postal code. GET /postcodes/{postal_code}/ — returns boundaries_centroid, boundaries_concordance, representatives_centroid, representatives_concordance; optional sets query param restricts to a boundary set.
Action
List boundariesPaginated list of electoral boundaries. GET /boundaries/ (optionally /boundaries/{boundary_set}/, or comma-separated multiple sets via ?sets=); filterable by name/external_id.
Action
List boundaries covering a pointFind electoral boundaries containing a given latitude/longitude. GET /boundaries/?contains={lat},{lng} (optionally scoped to a boundary set via /boundaries/{set}/?contains=...).
Action
List boundary setsList available boundary sets (groups of electoral districts, e.g. federal-electoral-districts, toronto-wards). GET /boundary-sets/; filterable by name/domain. GET /boundary-sets/{slug}/ for a single set.
Action
List candidatesPaginated list of electoral candidates for tracked elections. GET /candidates/ — behaves like /representatives/, filterable by name, first_name, last_name, gender, district_name, party_name.
Action
List representativesPaginated list of elected officials. GET /representatives/ (optionally /representatives/{representative_set}/); filterable by name, first_name, last_name, gender, district_name, elected_office, party_name.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews