Integration
Connect Sender to Represent by Open North
When something happens in Sender, 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 Sender 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 Sender and Represent by Open North
Triggers and actions 4 triggers · 17 actions
Trigger
New GroupTriggers when a new group is created.
Trigger
New SubscriberTriggers when a new subscriber is added.
Trigger
New Unsubscriber From GroupTriggers when a subscriber is removed from a group.
Trigger
Updated SubscriberTriggers when a subscriber is updated.
Action
Add groupCreate a new subscriber group. Endpoint: POST /v2/groups
Action
Add Subscriber to GroupAdds a subscriber to a group.
Action
Add / Update SubscriberAdds a new subscriber. If subscriber with the same email exists, updates the subscriber's data.
Action
Create CampaignCreates a draft campaign
Action
Get campaignRetrieve details of a single campaign by campaign id. Endpoint: GET /v2/campaigns/{campaign_id}
Action
Get subscriberRetrieve a single subscriber's data by email or subscriber id. Endpoint: GET /v2/subscribers/{subscriber_id}
Action
List groupsList all subscriber groups on the account. Endpoint: GET /v2/groups
Action
List subscribersList all subscribers on the account, paginated. Endpoint: GET /v2/subscribers
Action
Remove Subscriber From GroupRemoves a subscriber from a group.
Action
Unsubscribe EmailUnsubscribes an email address.
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.