Pointagram is a gamification tool that increases motivation and team achievements. Keep your team goal-oriented and celebrate great performance together.
Pointagram is a gamification tool that increases motivation and team achievements. Keep your team goal-oriented and celebrate great performance together. On Nagent, Pointagram is exposed as a fully-configurable productivity integration that any agent can call — 8 actions, and API key authentication. No code is required to wire Pointagram into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Pointagram to automate the kinds of tasks productivity teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Pointagram into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Pointagram, with input parameters and output schema. Drop these into any step of an agent built in Helix.
POINTAGRAM_ADD_SCORETool to add points to Pointagram players in a score series. Use when you need to award points with optional tags, descriptions, and automatic player creation.
Input parameters
Tags displayed with points. Each tag should have a 'name' field.
Number of points to award. Use this OR pointtype_name.
Description visible in the news feed about this score entry.
Internal Pointagram player identifier. Use this if you have the player's ID.
Sets transaction timestamp in datetime format (e.g., ISO 8601).
Player's display name for identification. Use when player_id is not available.
Player's email address for identification. Use when player_id is not available.
Set to 1 to automatically create missing players. Leave unset or set to 0 to not create players.
Named point type to assign. Use this OR points.
ID of the target score series. Use this OR scoreseries_name.
Transaction identifier. Reusing this ID will revoke the previous entry with the same ID.
Name of the target score series. Use this OR scoreseries_id.
Your system's unique player identifier. Use for integration with external systems.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
POINTAGRAM_LIST_COMPETITION_PLAYERSTool to fetch competition players and standings in Pointagram. Returns detailed player rankings, scores, and competition participation data. Use when you need to retrieve player standings, competition leaderboards, or analyze player performance across competitions.
Input parameters
Filter by specific player ID to get their competition participation.
Filter players by specific competition ID. If not provided, returns players from all competitions.
Filter by external player identifier from your system.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
POINTAGRAM_LIST_COMPETITIONSTool to fetch competitions in Pointagram with optional filtering. Use when you need to retrieve competition information including rankings and scores. Supports filtering by player (email, name, external ID), competition ID, or access key.
Input parameters
The search value to match against the criteria specified in search_by parameter. Used to filter competitions by player information.
Filter results to show only competitions associated with a specific access key identifier.
Specifies the search criteria type to filter competitions by player. Accepts 'Email', 'Name', or 'External Id'. Used in combination with 'filter' parameter.
Filter results to show only a specific competition by its unique ID. When provided, returns data for a single competition.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
POINTAGRAM_LIST_PLAYERSTool to fetch and list players in Pointagram with optional filtering. Use when you need to retrieve player information including name, email, external ID, and status. Supports filtering by email, name, or external ID.
Input parameters
The search value to match against the specified search_by field. Used in combination with 'search_by' parameter to filter results.
Specifies the search field to filter players. Accepts 'Email', 'Name', or 'External Id'. If provided, 'filter' parameter must also be provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
POINTAGRAM_LIST_SCORE_SERIESTool to list all score series in Pointagram. Use when you need to retrieve all configured score series collections that track and measure different point types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
POINTAGRAM_LIST_SCORE_SERIES_HISTORYTool to fetch historical point data for a score series. Returns time-series data of points awarded over time with optional filtering by tags, teams, players, and time range. Use when you need to retrieve historical transaction data for a specific score series.
Input parameters
Maximum rows per request (default: 50, maximum: 1000).
End time in UTC format "YYYY-MM-DD HH:MM:SS".
For pagination - use previous response's last row ID. Must be used together with offset_timestamp.
Start time in UTC format "YYYY-MM-DD HH:MM:SS".
Filter by specific tags in JSON format: \[{"id":"13","type":1},{"id":"14","type":1}\] where type 1=tags, type 2=point type.
Set to 1 to include revoked points; default is 0.
Filter by team IDs in JSON format: \["20"\].
Filter by player profile IDs in JSON format: \["19145"\].
The ID of the score series to fetch history for. This is a required parameter.
Alternative tag filtering with OR logic. Same format as tags_filter: \[{"id":"13","type":1}\].
For pagination - use previous response's last row timestamp. Must be used together with offset_id.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
POINTAGRAM_LIST_SCORE_SERIES_POINT_TYPESTool to fetch point types for a specific score series in Pointagram. Use when you need to retrieve the different types of points that can be awarded within a score series.
Input parameters
Id of the score series to fetch Point Types for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
POINTAGRAM_LIST_TEAMSTool to fetch and list all teams in Pointagram. Returns team information including ID, name, and icon. Use when you need to retrieve all available teams.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 54 agents privately built on Nagent that already use Pointagram.
Build on Nagent
Connect Pointagram to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Pointagram, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Pointagram is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Pointagram is connected, you configure its 8 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Pointagram steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Pointagram event fires, the agent kicks off automatically.
Every Pointagram action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Pointagram ships with 8 pre-built productivity actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Pointagram together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Pointagram-based workflows tailored to your business.