Raklet
CRMConnect AI agents to Raklet, a membership and community management platform. Agents create and enrich contacts, manage tags and subscriptions, record donations and debts, publish posts, and read the events the community runs.
What This Integration Enables
Raklet is built for organizations where the member list and the money are the same list: associations, alumni networks, clubs, and nonprofits, where a person's tags, plan, unpaid debts, and donation history all hang off one contact record. That is the reason this connector is worth wiring up, and it is also the reason to be careful with it. FlowRunner agents work the full model: search, create, update, and delete contacts; add emails, phones, addresses, work experience, and a photo to a contact and set which email is primary; create tags, add and remove members in bulk, and read a tag's membership back; list membership plans and create or delete subscriptions; list and record payments, create debts, and list or create donations; publish, list, and delete posts on the community feed and read the board; read events with their ticket options; and read organization settings, contact fields, corporate members, and the action log.
Three mechanics matter when you build against it. Search Contacts assembles filters into Raklet's base64 encoded query parameter over attribute paths, and the documented comparison operator is contains, so run Get Contact Fields first to learn the attribute names in your organization, and treat every match as approximate rather than exact. First name, last name, and language are required on both create and update, and an update replaces those fields, so an agent has to send current values for anything it does not intend to change. And several fields are numeric codes that Raklet's specification publishes as integers without publishing names for them, so currency, payment method, debt type, post status, and post permission type are exposed as plain numbers rather than as dropdowns with invented labels. On events, the position is plain: this connector has no triggers, because the Raklet API exposes no webhook subscription endpoints and no documented event payload shape, so no honest realtime or polling trigger could be built. Change detection runs off List Action Logs with a date range. The connector is built and verified against Raklet's official API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Signups That Arrive Already Segmented
New members register through a form or a website. Rather than exporting a file and importing it once a month, the agent calls Get Contact Fields to learn the attribute names in use, calls Search Contacts to check for an existing record by email or name, and calls Create Contact for the genuinely new people with their first name, last name, and language set. It then calls Add Members To Tag to place each new member into the chapter, cohort, or interest segment they selected. A membership coordinator opens Raklet and finds the roster already sorted rather than a queue of unfiled registrations.
Event Money Reconciled Against Members
An association takes payments at an in-person event through a card reader or a Stripe checkout. The agent reads each successful payment, calls Search Contacts to resolve the payer to a member record, and calls Record Payment to bring the amount into that member's balance. Where the payment covers a membership term, it calls Create Subscription against the right plan from List Membership Plans. Where the payment is a gift rather than dues, it calls Create Donation so campaign totals stay accurate. The treasurer stops reconciling a spreadsheet against a member list by eye.
An Announcement That Reaches the Right Segment
A board decision needs to reach one part of the community and not all of it. The agent calls List Tags and List Tag Members to read the current membership of the relevant segment, calls Create Post to publish the announcement to the community feed with the appropriate post permission type, and posts the segment size and the published post to a Slack channel for the organizers. Where the announcement also needs to go out by email, it calls List Tag Members and mirrors the segment into Brevo so the mailing goes to exactly the people the tag contains rather than to a list somebody exported last quarter.
Human-in-Loop Highlight
The dangerous operation in a membership database is not a bad write, it is a confident merge. Raklet's own documentation is explicit that Delete Contact is irreversible and that removing a contact removes the organization membership along with it, so a deduplication agent that decides two records are the same person is deciding to erase one member's membership record, their tags, their subscription, and their payment history. And the tool that agent has for deciding is Search Contacts, whose documented comparison operator is contains, which means the match is approximate by construction. Two members of the same family, a maiden name and a married name, a person who joined twice with a work and a personal address: the query cannot tell those apart, and neither can a threshold. So the agent gathers rather than decides. It runs Search Contacts, calls Get Contact Details on every candidate, and posts to the membership coordinator: "Possible duplicate: [name] appears as [n] records. Record A joined [date], has [n] tags, [n] payments totalling [amount], subscription [plan]. Record B joined [date], has [n] tags, [n] payments totalling [amount]. Differences: [fields]. Which record survives, or are these different people?" The coordinator answers, and only then does the agent call Update Contact on the survivor and Delete Contact on the other, remembering that an update replaces first name, last name, and language, so current values go with it. Creating members, tagging them, and recording their payments runs unattended. Deciding that two people are one person is human-in-the-loop work, because the platform gives you no way to take it back.
Agent Capabilities
37 actionsContacts
5- Search Contacts Searches contacts using Raklet's base64 encoded query parameter over attribute paths such as `attributes.firstName`, with `contains` as the documented comparison operator. Used for duplicate checks and segment lookups, with the understanding that matches are approximate.
- Get Contact Details Retrieves the full record for a single contact. Used to pull the evidence behind a possible duplicate before anyone decides what to do about it.
- Create Contact Creates a new contact. First name, last name, and language are required. Used when a signup, registration, or import has no existing record.
- Update Contact Updates an existing contact. The update replaces first name, last name, and language, so current values must be sent for anything not being changed.
- Delete Contact Permanently removes a contact and the organization membership attached to it. This cannot be undone.
Contact Details
6- Add Contact Email Adds an email address to an existing contact. Used when a member supplies a second address rather than replacing the first.
- Set Primary Contact Email Marks one of a contact's addresses as primary. Used to control which address mailings and platform notices go to.
- Add Contact Phone Adds a phone number to a contact record.
- Add Contact Address Adds a postal address to a contact record. Used for chapter assignment and for physical mailings.
- Add Contact Work Experience Adds a work experience entry to a contact. Used to keep an alumni or professional directory current from an external source.
- Set Contact Photo Sets the photo on a contact record. Used when a member uploads a picture through a form or portal elsewhere.
Tags
5- List Tags Returns the tags defined in the organization. Used to resolve a segment name to the tag an agent will write against.
- Create Tag Creates a new tag. Used when a flow needs a segment that does not exist yet, such as a cohort or an event audience.
- Add Members To Tag Adds one or more contacts to a tag in a single call. Used to build a segment in bulk from live roster data before a mailing or an invitation.
- Remove Members From Tag Removes one or more contacts from a tag. Used to retire a segment or to drop members who no longer qualify.
- List Tag Members Returns the contacts currently in a tag. Used to read a segment back before acting on it, and to mirror it into an email tool.
Memberships
4- List Membership Plans Returns the membership plans configured in the organization. Used to map a payment or a signup to the correct plan.
- List Subscriptions Returns subscriptions with their terms. Used for renewal reporting and for checking whether a member is current.
- Create Subscription Assigns a membership plan to a contact and starts the term. Used when a payment or an approval confirms membership.
- Delete Subscription Removes a subscription. This is irreversible, so it belongs behind a review step.
Finance
6- List Payments Returns recorded payments. Used for reconciliation and treasurer reporting.
- Record Payment Records a payment against a member. This brings money collected outside Raklet into the member's balance; it does not process a charge. Payment method is a numeric code published by Raklet without published names, so read an existing payment to find the code your organization uses.
- List Debts Returns outstanding debts. Used to build a dues reminder list from live data.
- Create Debt Creates a debt against a member. Debt type is a numeric code. Used to record dues or fees owed.
- List Donations Returns recorded donations. Used for campaign totals and acknowledgement flows.
- Create Donation Records a donation against a member and campaign. Used to bring gifts taken elsewhere into the totals the development team reports on.
Posts
4- List Posts Returns community feed posts.
- Create Post Publishes a post to the community feed, with a post status and permission type given as numeric codes. Used to push an announcement from an upstream system to the members who should see it.
- Delete Post Removes a post. This is irreversible.
- List Board Posts Returns posts from the board. Used to read governance announcements separately from the general feed.
Events
3- List Events Returns events within a bounded date range. Raklet rejects the call without both a start date and an end date.
- Get Event Retrieves a single event with its detail.
- List Event Ticket Options Returns the ticket options for an event, including their counts. Used to report remaining capacity to organizers.
Organization
4- Get Contact Fields Returns the contact attribute names available in the organization, custom fields included. Run this first, because it is what tells an agent the attribute paths a Search Contacts predicate can use.
- Get Organization Settings Returns the organization's configuration.
- List Action Logs Returns the action log for a date range. This is the change detection surface, since the connector exposes no triggers.
- List Corporate Members Returns corporate member records. Used for sponsor and partner reporting.
Frequently Asked Questions
What can FlowRunner do with Raklet?
FlowRunner agents can run Search Contacts, Get Contact Details, and Create Contact in Raklet, plus 34 more actions.
Does connecting Raklet to FlowRunner require OAuth?
No. Raklet connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Raklet trigger a FlowRunner workflow automatically?
Raklet doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Raklet
$100 in credits. No card required. Connect in minutes.