Flaree
HRConnect AI agents to Flaree, the employee recognition platform where colleagues send each other point-bearing cards. Agents trigger recognition off real milestones instead of a quarterly reminder.
What This Integration Enables
Flaree is a small API and that is a position, not a gap. Three actions: send a card, list the cards, validate the key. There is no analytics endpoint, no leaderboard, no balance report. The platform has decided that the interesting thing is the transfer itself, and the connector inherits that focus. What a FlowRunner agent adds is timing. Recognition programmes fail on latency far more often than on design. The moment worth marking happens on a Tuesday inside a ticketing tool, and the person who would have marked it finds out on Friday. By then the specific thing that was good has blurred into a general thing that was fine.
An agent sits where the milestone actually occurs. It sees the deal close, the release ship, the escalation get resolved, the referral convert, and it can compose a card the same hour with the evidence still attached. Send Flaree carries a receiver email, a card name, a point value between 1 and 100, an optional comment and an optional giver, and Flaree will reject a transfer where either party is outside the organization or the giver lacks transfer permission. Validate API Key doubles as a membership check, which is the guard an agent should run before it tries. There is one deliberate escape hatch worth knowing: a transfer can be marked as a system transfer, which attributes it to the Flaree Assistant rather than to a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Recognition at the moment the work lands
An escalated support case is resolved and the customer leaves a strong rating. The agent reads the ticket, identifies the resolver, confirms with Validate API Key that they exist in the organization, and drafts a card: which case, what the customer said, what the resolver did that was unusual. Instead of sending it, the agent puts the draft in front of the team lead. The lead adjusts the point value, confirms it should go out under their own name, and the transfer completes with the customer's words in the comment.
Anniversaries and onboarding milestones on a schedule
A scheduled flow reads the HR roster each morning and finds the people hitting a work anniversary or completing their first month. For these, there is no ambiguity and no individual giver, so the agent sends each card as a system transfer attributed to the Flaree Assistant, with a comment naming the milestone. Nobody's personal recognition budget is spent and nobody is credited with a message they did not write. Calendar recognition is exactly the category that should be automated without a signature.
Nominations that survive the trip to a decision
Internal nominations arrive through a form. The agent groups them by nominee, resolves each nominee against the organization, matches the described achievement to a card from List Flaree Cards, and proposes a point value scaled to the nomination volume and the type of contribution. The People Ops lead sees one consolidated view rather than a spreadsheet of free text, approves the set, and the agent sends the transfers. The judgment stays human. The collation, deduplication and lookup do not.
Human-in-Loop Highlight
There are two irreversible things about Send Flaree, and the second one is the one people miss. The first is ordinary: points carry value in the organization's redemption catalogue and the API offers no way to revoke a transfer, so a card sent against a deal that later gets reopened, or a release that gets rolled back, cannot be taken back. The second is that the Giver Email field lets a flow send recognition signed by a colleague who never wrote it. A card that arrives saying it came from a named teammate, with a warm comment that teammate has never read, is not a small automation liability. It is the difference between a programme people trust and one they quietly stop believing.
So FlowRunner treats attribution as the human-in-the-loop moment, not the detection. The agent finds the milestone, confirms both parties with Validate API Key, picks the card and drafts the comment, then stops and asks the named giver directly through Slack or email: "You closed the Harlow escalation with Priya. I have a Flaree ready to send from you to Priya, 40 points: 'Stayed on the Harlow migration past midnight and got their reporting back before their board meeting.' Send it as written, edit the wording, or send it from the Flaree Assistant instead?" One reply resolves it. Anything with a person's name on it got that person's consent, and anything on a calendar goes out as a system transfer where no signature is implied. The agent handles the watching, which no human does well. The human handles the words, which no agent should own.
Agent Capabilities
3 actionsRecognition
1- Send Flaree Sends a Flaree card to a colleague, transferring recognition points to them. Takes the receiver's email, the name of the card to transfer and a point value from 1 to 100, with an optional giver email, an accompanying comment, and a system transfer switch that attributes the card to the Flaree Assistant instead of a person. Both parties must exist in the organization behind the API key, the giver must hold transfer permission, and the card name must match an existing card. Used at the moment a milestone is detected, once a person has confirmed the attribution.
Flaree Cards
1- List Flaree Cards Returns every Flaree card available to the organization behind the configured API key, each with its identifier and name. Send Flaree identifies cards by name rather than by id, so this is the lookup step that keeps an automated transfer from failing on a renamed card, and the source an AI step reads when choosing which card fits an achievement.
Account
1- Validate API Key Verifies that the configured API key is valid and returns the company it belongs to. Supplying an email address additionally checks whether that person exists in the organization, returned in the metadata property. Used as a connection health check, and more usefully as the guard that confirms a giver or receiver is a member before a transfer is attempted.
Frequently Asked Questions
What can FlowRunner do with Flaree?
FlowRunner agents can run Send Flaree, List Flaree Cards, and Validate API Key in Flaree.
Does connecting Flaree to FlowRunner require OAuth?
No. Flaree connects to FlowRunner with an API key, no OAuth flow required.
Can Flaree trigger a FlowRunner workflow automatically?
Flaree doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Flaree
$100 in credits. No card required. Connect in minutes.