GitHub Gist is a service provided by GitHub that allows users to share code snippets, notes, and other text-based content. It supports both public and private gists, enabling easy sharing and collaboration.
GitHub Gist is a service provided by GitHub that allows users to share code snippets, notes, and other text-based content. It supports both public and private gists, enabling easy sharing and collaboration. On Nagent, Gist is exposed as a fully-configurable developer tools integration that any agent can call — 20 actions, and API key authentication. No code is required to wire Gist into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Gist to automate the kinds of tasks developer tools 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 Gist 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 Gist, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GIST_CHECK_GIST_STARCheck if the authenticated user has starred a specific gist. Returns True if the gist is starred, False if not starred or if the gist doesn't exist. This is a read-only, idempotent operation that requires authentication but no special permissions.
Input parameters
The unique identifier of the gist to check. Can be a short numeric ID (e.g., '1305321') or a longer alphanumeric hash (e.g., 'aa5a315d61ae9438b18d').
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
GIST_CREATE_GISTTool to create a new gist with one or more files. Use when you need to create a code snippet or text file to share. Note: Do not name your files 'gistfile' with a numerical suffix.
Input parameters
Names and content for the files that make up the gist. Each key is a filename (do not name files 'gistfile' with a numerical suffix), and each value contains the file content.
Flag indicating whether the gist is public. Defaults to false (private gist).
Description of the gist.
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
GIST_CREATE_GIST_COMMENTTool to create a comment on a gist. Use when you need to add a comment to an existing gist.
Input parameters
The comment text to add to the gist.
The unique identifier of the gist to comment on.
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
GIST_DELETE_GISTTool to delete a gist. Use when you have a gist_id and want to permanently remove that gist. Example prompt: "Delete gist 'aa5a315d61ae9438b18d'".
Input parameters
The unique identifier of the gist to delete. Can be a short numeric ID (e.g., '1305321') or a longer alphanumeric hash (e.g., 'aa5a315d61ae9438b18d').
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
GIST_DELETE_GIST_COMMENTTool to delete a comment on a gist. Use when you have both the gist_id and comment_id and want to remove that comment. Example prompt: "Delete comment 42 from gist 'aa5a315d61ae9438b18d'".
Input parameters
The unique identifier of the gist containing the comment. Obtain this from list_gists or other gist operations.
The unique identifier of the comment to delete. Obtain this from list_gist_comments or get_gist_comment operations.
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
GIST_FORK_GISTTool to fork a gist. Use when you need to create a copy of an existing gist under your own account.
Input parameters
The unique identifier of the gist to fork.
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
GIST_GET_GISTTool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
Input parameters
The unique identifier of the gist.
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
GIST_GET_GIST_COMMENTTool to get a specific comment on a gist. Use when you need to retrieve details of a particular comment given gist_id and comment_id.
Input parameters
The ID of the gist
The ID of the comment
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
GIST_GET_GIST_REVISIONTool to retrieve a specific gist revision. Use when you need details of a past state for an existing gist by commit SHA.
Input parameters
The commit SHA of the desired revision.
The unique identifier of the gist.
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
GIST_LIST_GIST_COMMENTSTool to list comments on a gist. Use after confirming the gist_id to retrieve comments for a specific gist. Example: 'List comments for gist abc123'.
Input parameters
Page number to fetch. Default: 1.
The ID of the gist to list comments for
Results per page (max 100). Default: 30.
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
GIST_LIST_GIST_COMMITSTool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
Input parameters
Page number of the results to fetch
Response media type. Recommended: application/vnd.github+json
The unique identifier of the gist to list commits for.
Number of results per page (max 100)
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
GIST_LIST_GIST_FORKSTool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist.
Input parameters
Page number to fetch. Default: 1
The ID of the gist to list forks for
Results per page (max 100). Default: 30
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
GIST_LIST_GISTSTool to list the authenticated user's gists or all public gists if called anonymously. Use after setting a valid GitHub token in headers.
Input parameters
Page number of results to fetch. Default: 1 if not provided.
Only show gists last updated after this ISO 8601 timestamp (YYYY-MM-DDTHH:MM:SSZ)
Media type for the response. Example: 'application/vnd.github+json'
Number of results per page (1-100). Default: 30 if not 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
GIST_LIST_PUBLIC_GISTSTool to list public gists sorted by most recently updated. Use when you need to discover recent public gists. Note: with pagination, you can fetch up to 3000 gists.
Input parameters
Page number of results to fetch. Default: 1 if not provided.
Only show gists last updated after this ISO 8601 timestamp (YYYY-MM-DDTHH:MM:SSZ)
Number of results per page (1-100). Default: 30 if not 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
GIST_LIST_STARRED_GISTSTool to list the authenticated user's starred gists. Use when you need to retrieve all gists the user has starred.
Input parameters
Page number of the results to fetch
Only list gists updated after this ISO 8601 timestamp (YYYY-MM-DDTHH:MM:SSZ)
Response media type. Recommended: application/vnd.github+json
Number of results per page (max 100)
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
GIST_LIST_USER_GISTSTool to list public gists for a specified GitHub user. Use when you have a username and need their gists.
Input parameters
Page number of results to fetch.
Only show gists updated after this ISO 8601 timestamp (YYYY-MM-DDTHH:MM:SSZ)
Number of results per page (1-100).
The handle for the GitHub user account
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
GIST_STAR_GISTStar a GitHub gist. This operation is idempotent and will succeed even if the gist is already starred.
Input parameters
The unique identifier of the gist to star. Can be a short numeric ID (e.g., '1305321') or a longer alphanumeric hash (e.g., 'aa5a315d61ae9438b18d').
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
GIST_UNSTAR_GISTUnstar a GitHub gist. This operation is idempotent and will succeed even if the gist is not currently starred.
Input parameters
The unique identifier of the gist to unstar. Can be a short numeric ID (e.g., '1305321') or a longer alphanumeric hash (e.g., 'aa5a315d61ae9438b18d').
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
GIST_UPDATE_GISTTool to update a gist's description and files. Use when you need to modify gist content, rename files, or delete files from a gist.
Input parameters
The gist files to be updated, renamed, or deleted. Each key must match the current filename (including extension) of the targeted gist file. For example: 'hello.py'. To delete a file, set the value to null. For example: {'hello.py': None}. To update content, provide {'hello.py': {'content': 'new content'}}. To rename, provide {'hello.py': {'filename': 'goodbye.py'}}.
The unique identifier of the gist to update.
The updated description of the gist.
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
GIST_UPDATE_GIST_COMMENTTool to update a Gist comment. Updates an existing comment on a gist. You must be the author of the comment to update it.
Input parameters
The updated text for the comment.
The ID of the Gist to which the comment belongs.
The ID of the comment to update.
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 59 agents privately built on Nagent that already use Gist.
Build on Nagent
Connect Gist 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 Gist, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Gist is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Gist is connected, you configure its 20 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Gist 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 Gist event fires, the agent kicks off automatically.
Every Gist 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 Gist ships with 20 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Gist together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Gist-based workflows tailored to your business.