
The Gleap Connector brings customer support and feedback into ShareBuilder Assistant Skills. Media teams can turn a new ticket into a coordinated follow-up, give support staff useful customer context, create tickets from approved requests, and keep the conversation connected to the work happening around it.
The connector helps sellers and operations teams move each request, its details, and the next step to the people responsible for getting it resolved.
About Gleap
Gleap is a customer support and feedback platform for software teams. It brings support conversations, bug reports, and product feedback together so teams can understand the problem and coordinate a response.
For media organizations using Gleap, that can include questions about a customer portal, problems with an internal sales tool, reporting issues, and requests for a better workflow. Connecting those conversations to sales and operations helps the people closest to the customer stay informed.
This is the Gleap Connector
The Gleap Connector includes a New Ticket Received trigger and six actions: Create Ticket, Get Ticket, Search Tickets, Update Ticket, Add Ticket Message, and Create or Update Contact Session.
The trigger starts a Skill when Gleap sends a new-ticket webhook to the workflow’s callback URL. The actions let that Skill retrieve the details, create or update a support record, add a message, and maintain approved contact information. A Skill can also begin from another connected system or a scheduled review.
Give new requests a clear next step
New Ticket Received passes ticket information into a Skill, including the ticket ID and available details such as title, description, type, status, priority, customer reference, and screenshot URL.
A workflow could use that information to:
- alert the operations team when a customer reports a campaign-reporting problem
- route a sales-tool question to the team responsible for that product
- bring a new feedback item into an internal review queue
- retrieve the ticket before preparing a handoff to another team
Get Ticket retrieves a specific ticket by ID, giving later steps a way to work from the current record. The workflow should keep that ID with any related work so an update goes back to the right conversation.
Routing rules belong to the Skill. Teams decide which requests need immediate attention, who owns the next step, and when a person should review the details before work continues.
Create support tickets without retyping the request
Create Ticket can turn an approved request from another workflow into a Gleap support or feedback ticket. It supports a title and additional information such as a description, ticket type, priority, status, customer session, tags, attachments, and due date.
A seller could collect a customer’s issue through an established intake process. A Skill could then create the Gleap ticket with the approved description and customer reference, preserving the original context for the support team.
Operations teams can also record issues discovered during routine work. A reporting check could create a ticket with the relevant details when it identifies a problem that needs investigation.
Ticket creation should include a duplicate check or a stored reference to the originating request. Re-running a workflow shouldn’t create a second support case for the same problem.
Keep ownership and ticket details current
Update Ticket supports changes to fields including title, description, status, priority, assigned user or team, tags, due date, and custom data. It also supports archive and snooze settings.
These actions can help maintain a useful support queue as information becomes available. A Skill could route a reviewed request to the appropriate team, add an agreed due date, or update the description with details collected during a follow-up.
For example, an advertiser’s reporting question may turn out to require a data-team investigation. The workflow can update the ticket’s ownership and add the confirmed context while keeping the existing ticket as the record of the request.
Use verified user and team IDs, and define which fields each workflow owns.
Keep the conversation with the work
Add Ticket Message adds a public comment, a customer comment, or an internal note to an existing ticket. This lets a Skill record a handoff, add an investigation summary, or deliver a reviewed response through the same support record.
A workflow could create a related Jira issue and then add an internal note containing the issue reference. When a person confirms the resolution and approves the response, another step could add the customer-facing update to Gleap.
Internal notes and public replies serve different audiences. Skills should set message visibility deliberately and require the appropriate review before sending customer-facing claims, commitments, or resolution details.
Bring customer context into support
Create or Update Contact Session maintains a Gleap session/contact record for a known customer. Supported information includes a user ID, name, email, phone, company details, tags, and custom data.
A Skill could bring approved company and contact details from the customer onboarding process into Gleap. That can help support staff understand which organization the request belongs to without asking the customer to repeat basic information.
Use a dependable customer identifier and send only the information needed for support. A contact update should use an intentional field mapping rather than copy an entire CRM record.
Review the queue before issues get lost
Search Tickets can filter by ticket type, status, priority, archive state, and spam state, with sorting and pagination. A scheduled Skill could gather open high-priority tickets for an operations review or prepare a focused list for a support meeting.
The workflow can retrieve selected tickets and route a focused review through another connected tool, with clear ownership and follow-up.
Assistant Skills
Skills are the workflows you train the ShareBuilder Assistant to run for your team. Create a Skill and the Assistant executes playbooks, coordinates processes, updates systems, and communicates across platforms automatically.
Availability
The Gleap Connector is included in the current Assistant Skills production catalog. A Gleap project ID and API token are required. New-ticket workflows also require manual configuration in Gleap under Developer → Webhooks. Project access, API limits, and customer enablement apply.
For more information
To learn more about ShareBuilder Assistant Skills or discuss using the Gleap Connector in your support workflows, visit ShareBuilder Assistant Skills or contact ShareBuilders.
About ShareBuilders
ShareBuilders delivers a media-focused sales platform that includes Pricing, CRM, Data Enrichment, and workflow automation. Built specifically for media organizations, ShareBuilders helps teams manage pipelines, activity, pricing, and performance with secure cloud access and mobile tools designed for sellers on the go.



