Integration
Connect Wistia to Represent by Open North
When something happens in Wistia, 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 Wistia 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 Wistia and Represent by Open North
Triggers and actions 2 triggers · 22 actions
Trigger
New mediaTriggers when a new media is uploaded to your Wistia account.
Trigger
New projectTriggers when a new project is created in your Wistia account.
Action
Copy mediaCopy a media to a destination project.
Action
Copy projectCopy an existing project, including all of its medias.
Action
Create projectCreate a new project in your Wistia account.
Action
Delete mediaDelete a media by its hashed id.
Action
Delete projectDelete a project and all of its medias.
Action
Get accountRetrieve information about your Wistia account.
Action
Get mediaRetrieve a single media by its hashed id.
Action
Get media customizationsRetrieve the player customizations (embed options) for a media.
Action
Get media statsRetrieve aggregated engagement statistics for a media.
Action
Get projectRetrieve a single project by its hashed id, including its medias.
Action
List mediasList medias, optionally filtered by project, name, or type.
Action
List projectsList all projects in your Wistia account.
Action
Update mediaUpdate a media's name or description.
Action
Update media customizationsReplace the player customizations (embed options) for a media. Provide a JSON object of customization keys.
Action
Update projectUpdate an existing project's attributes.
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