Pointagram
ProductivityConnect AI agents to Pointagram, a gamification platform for sales and support teams. Agents create players and teams, award points to score series, and read competitions and leaderboards so performance incentives update automatically as work gets done.
What This Integration Enables
Pointagram exists to make invisible work visible: calls made, tickets resolved, deals closed, all rolled into score series, teams, and competitions that people actually look at. The problem with gamification has never been the concept, it is the data entry. A leaderboard maintained by hand is stale by the time anyone reads it, and stale leaderboards stop being motivating within about a week.
FlowRunner agents close that gap. They create players and teams, award points to score series with a point type and tags, move players between teams, and read competitions and standings back out for dashboards and channel posts. Add Score is the core operation and everything else supports it: List Score Series resolves the container, List Score Series Point Types resolves what kind of point applies, and List Score Series History reads back who scored what and when for reconciliation.
Scoring is also, quietly, a compensation-adjacent activity. People compare themselves to the board, and in some organizations the board decides who gets recognized at the end of a quarter. So the platform default here is human-in-the-loop in its most literal form: the agent does the entry, and a person owns the one decision that can corrupt the record, which is described below.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Closed deals score themselves
A deal reaches Closed Won in Pipedrive. The agent resolves the score series with List Score Series, resolves the applicable point type with List Score Series Point Types, and calls Add Score for the owning rep with the deal name in the comment and a tag identifying the product line. It then calls List Competition Players and posts the top five standings into the team channel in Slack with the change since yesterday. The board is current because it is written by the same event that closed the deal.
Support quality, not just support volume
A support team runs a quarterly competition. Rather than scoring ticket count, which rewards closing tickets fast, the agent reads resolved tickets from Zendesk, waits for the satisfaction response, and calls Add Score only when the rating clears the threshold, with a tag recording the rating. Because Add Score accepts a custom score time, the points land on the date the ticket was resolved rather than the date the rating arrived, so the daily board stays honest.
Team setup for a new competition
A new quarter starts and the field is being reorganized. The agent calls Create Team for each new pod, then calls Add Player To Team and Remove Player From Team to reshape membership from the current org chart. Removing a player from a team detaches them from that team only; they stay in the account with their history intact. The agent posts the proposed membership changes for the sales manager to confirm before it applies them, since team membership decides which leaderboard a person appears on.
Human-in-Loop Highlight
Add Score has an option called Create Player that auto-creates a player when the person is identified by name or email and does not yet exist. It is a convenience that turns into a data-integrity problem the moment the identifier is imperfect. A rep whose CRM record carries a personal email, a married name, or a middle initial that the Pointagram player does not have will not match, and with auto-create enabled the flow does not fail. It silently mints a second player and starts awarding that person's points to a duplicate identity, in the middle of a live competition, on a board the whole team is watching. Unwinding it is worse than it sounds, because Remove Player permanently deletes a player from the account, taking their scoring history with them.
So the agent gates the creation, not the scoring. Every Add Score call is preceded by List Players filtered on the identifier, and Create Player stays off. When the lookup returns exactly one player, the points go in unattended. When it returns none or more than one, the agent stops and asks the competition owner: "Closed Won deal for [email protected] does not match a Pointagram player. Nearest matches are Jan Novak, player 4417, and J. Novak, player 4902, both scoring in the Q3 series. Award to 4417, award to 4902, create a new player, or hold the score?" The score waits. It is a much cheaper thing to hold for an hour than a leaderboard that has to be explained afterward.
Agent Capabilities
14 actionsConnection
1- Test Connection Verifies the configured API key and login email against the Pointagram test endpoint. Used to confirm credentials before a flow runs, or after a key rotation.
Players
3- List Players Lists players, optionally filtered by a single attribute of email, name, or external id combined with a search value. Both online players with a login and offline players are returned. This is the lookup that keeps identities from splitting.
- Create Player Creates a player by name, with an email for an online player who can log in or the offline setting for one who cannot. Pointagram returns a conflict error when the identity already exists.
- Remove Player Removes a player identified by internal id, external id, or email. This permanently deletes the player from the account, so it is not the tool for reorganizing teams.
Scoring
4- Add Score Awards points to a player in a score series, the core scoring operation. The player is identified by internal id, external id, email, or name, and the series by id or name, with optional comment, tags, point type, and a custom score time. The Create Player option can auto-create an unmatched player, which is exactly why the identity lookup belongs first.
- List Score Series Lists the score series in the account, the containers that track who scored how many points and when. Used to resolve a series id before scoring.
- List Score Series Point Types Lists the point types configured for a series, so one series can track different kinds of points such as calls, meetings, and deals. Used to resolve the correct point type name for Add Score.
- List Score Series History Returns individual score entries for a series with player, points, time, and tags, filterable by time range and by whether revoked scores are shown, with paging. Used for reconciliation against the source system.
Teams
4- List Teams Lists the teams in the account, the groupings used for team-based competitions and leaderboards.
- Create Team Creates a team with a name and an icon, with an optional setting to exclude it from filtered leaderboards and reports.
- Add Player To Team Adds a player to a team, identifying the player by internal id, external id, or email.
- Remove Player From Team Detaches a player from a team. The player stays in the account with their history; only the team membership is removed.
Competitions
2- List Competitions Lists competitions, optionally narrowed by a search attribute and value or fetched by id. Used to resolve the competition a score belongs to.
- List Competition Players Returns the players in a competition with their standings. Used to build custom leaderboards and dashboards outside Pointagram.
Frequently Asked Questions
What can FlowRunner do with Pointagram?
FlowRunner agents can run Test Connection, List Players, and Create Player in Pointagram, plus 11 more actions.
Does connecting Pointagram to FlowRunner require OAuth?
No. Pointagram connects to FlowRunner with an API key, no OAuth flow required.
Can Pointagram trigger a FlowRunner workflow automatically?
Pointagram doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Pointagram
$100 in credits. No card required. Connect in minutes.