Gleap icon

Gleap

All-in-one customer feedback platform for tickets, chat sessions, engagements, help center collections, and product-feedback features.

Tailored to product teams that triage and archive tickets, run chat conversations, design help center collections, and clone engagements across projects.

Example Use Cases

These are the Gleap actions Snow can use when building apps with you. Connecting an account does not make Snow run these on its own.

Create a new session

Create a new user session in Gleap and associate it with a project. Use this to track user activity, engagement metrics, and session data. Sessions can be created with minimal information and enriched later through identify_user or other API calls.

Get a session

Retrieves detailed information for a specific session by its ID. Use this when you need to fetch comprehensive session data including user information, activity timestamps, engagement metrics, and custom metadata for a particular session.

Get project

Retrieves complete details for a specific project by its ID. Use when you need to view project configuration, settings, notification preferences, or metadata for a single project.

Get Projects

Retrieves all projects accessible to the authenticated user. Use when you need to list all projects the user has access to. Rate limit: 1000 requests per minute.

Search for sessions

Search for sessions in Gleap using various filter criteria. Use when you need to find sessions by user ID, email, name, or other session attributes. Supports filtering by multiple criteria including user information (userId, email, name), session identifiers (gleapId, gleapHash), language, and user status (blocked, unsubscribed).

Search Tickets by Term

Search for tickets using a text search term in Gleap. Use when you need to find tickets based on keywords or phrases in titles and descriptions.

Update a ticket

Tool to update an existing ticket/bug in Gleap. Use when you need to modify ticket properties like status, priority, description, type, assigned user, tags, or other attributes. All fields except the ticket ID are optional - only provide the fields you want to update.

Archive a Ticket

Tool to archive a ticket. Use after confirming the ticket ID and that the ticket is resolved. Call when moving tickets to history.

Archive All Tickets

Tool to archive all tickets matching specific type and status criteria. Use when you need to bulk archive multiple tickets at once based on their type and status.

Clone Engagement

Tool to clone an existing engagement. Use when you need to duplicate an engagement with all its configuration.