Salesforce pushes outward: tickets in Gleap become cases in Salesforce, and updates follow. It suits teams whose support lives in Gleap but whose account management runs on Salesforce. Only project admins can connect it, and it needs the Team plan or higher.
Gleap_Content (API name Gleap_Content__c) of type Rich Text Area to your Case object, and use your production org. Gleap writes the ticket content into that field and signs in through login.salesforce.com, the production login. Without the field, Salesforce rejects the case and nothing arrives.Adding the field takes a minute in Salesforce Setup, under the Case object's fields, and it's the step people skip.
Go to Settings → Connectors, pick Integrations and click Add integration.
Pick Salesforce.
Enter your Salesforce address, for example https://your-company.my.salesforce.com.
Sign in to Salesforce and approve the connection.
The connection is authorised as the Salesforce user who set it up, so cases are created by that account rather than by the individual teammate.
A ticket sent to Salesforce creates a case, with the ticket title as its subject and the ticket content in Gleap_Content. Later changes to the ticket update the case, new messages on the ticket are added as case comments, and deleting the ticket deletes the case.
Open the Salesforce connection and click Send tickets.
Turn on Send tickets automatically.
Under Ticket types, keep only the types that represent real customer issues.
Turn on Don't send internal notes and Don't send personal data if those should stay in Gleap, then click Save.
The picker matters more here than anywhere else. Salesforce cases are usually reported on and often tied to process, so filling the org with "how do I export a CSV" distorts numbers other people rely on.
Or leave automatic sending off and send single tickets with Send to integration in the ticket's Integrations section; Forward new comments then keeps their comments flowing.
Check that the Gleap_Content field still exists and hasn't been renamed, and that the connected user still has permission to create cases. Both fail quietly: Gleap shows no error, and cases simply don't show up in Salesforce.