Gist is an all-in-one customer messaging and engagement platform that combines live chat, email marketing, chatbots, a knowledge base, and event tracking. The Gist connector reads contacts, tags, segments, events, conversations and conversation counts, drip campaigns, forms and form submissions, knowledge base articles and collections, ecommerce stores, teams, and teammates, and can create and update contacts, tag contacts, track events, manage conversations, write knowledge base content, and sync ecommerce stores, customers, products, and orders.
Power end-to-end data operations for your Gist API with Nexla. Our bi-directional Gist connector is purpose-built for Gist, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Gist or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Gist workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to the Gist API (https://api.getgist.com) with your Gist workspace's API key, which Gist accepts as a Bearer token in the Authorization header. To find the key:
Open Settings, and select API Key in the integration settings.
Copy the API key.
The API key gives access to your workspace's private contact data, so keep it within your company and don't share it publicly. See the Authentication section of the Gist API reference and Gist's Build an integration guide for details.
Gist API rate limits
The Gist API is limited to 100 requests per 10 seconds per workspace; requests over the limit receive an HTTP 429 response. Paged templates make one request per page of 50 records, so plan schedules for large workspaces accordingly. See Rate Limits.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Gist API key in the API Key Value field. Enter the key only; Nexla adds the Bearer prefix and sends it in the Authorization header of every request.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests the credential by reading the contact list from your Gist workspace.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Gist connector tile, then select the credential that will be used to connect to your Gist workspace, and click Next; or, create a new Gist credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Gist endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.
Templates that say "Results are paged automatically" read every page, 50 records at a time. Templates that need an ID read one object; use the matching list template to find the ID.
List all contacts in the workspace (users and leads)
Lists all contacts in the workspace, both users and leads, including each contact's ID, email address, name, user ID, tags, segments, and custom properties. Results are paged automatically, 50 records per page.
Retrieves the workspace ID, app ID, scopes, and expiry of the API key the credential uses. Use it to confirm which workspace the credential connects to.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Gist sources can also be manually configured to ingest data from any valid Gist API endpoint, including endpoints not covered by the pre-built templates, chained API calls to fetch data from multiple endpoints, or custom request parameters such as the optional filters on the contacts list. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Gist endpoint URLs take the form https://api.getgist.com/.... List responses wrap their records in a named array, for example $.contacts[*] for /contacts, and page with the page and per_page query parameters (50 records per page by default, at most 60). You do not need to add the Authorization header; Nexla adds it from your Gist credential. See the Gist API reference for the available endpoints.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Gist data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Gist destination, and select the Send to Destination option from the menu. Select the Gist connector from the list of available destination connectors, then select the credential that will be used to connect to your Gist workspace, and click Next; or, create a new Gist credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Gist endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each record in the Nexset is sent as the JSON body of one request, one record at a time. ID settings, such as a conversation or store ID, are fixed on the destination and apply to every record it sends, so each record acts on the same object. Templates marked Side effect delete data or message contacts in ways that cannot be undone from Nexla.
Creates a contact from each record, or updates the existing contact when the record's email or user_id matches one. Records can carry name, phone, custom_properties, and tags.
Queues a batch create-or-update of contacts. Each record holds a contacts array. Gist returns a batch_id; use the Get Contact Batch Import Status source template to follow the import.
Tracks an event for a contact from each record, for example {"event_name": "Clicked Signup Button", "email": "jane@example.com"}. Records can also carry properties and occurred_at.
No additional parameters are required.
Attach Contact to Subscription Type
Opts a contact in to a subscription type. Each record identifies the contact by email, user_id, or contact_id, with subscribed_status set to true.
Enter the ID. Use the List Subscription Types source template to find it.
Tags up to 50 contacts at once. Each record holds the tag name and a contacts array of objects with an id, email, or user_id. Gist creates the tag if it does not exist.
Removes a tag from contacts. Each record holds the tag id or name and a contacts array in which each contact has "untag": true. The contacts and the tag are not deleted.
Creates a conversation initiated by a contact from each record. Each record holds from (the contact's id, user_id, or email), body, and optionally title.
Adds a reply or an internal note to a conversation. Each record holds message_type (reply or note), body, and a teammate_id or the contact's id, user_id, or email.
Side effect: a teammate reply is sent to the contact.
Enter the Id. Use the List all conversations in the workspace source template to find it.
Subscribes a contact to a drip campaign, or unsubscribes them. Each record holds the campaign id and the contact's email or user_id; add "unsubscribed": true to unsubscribe.
Side effect: subscribing starts sending the campaign's emails to the contact.
Submits a form for a contact. Each record holds the form fields, consent, and page data. Gist creates or updates the contact and records a form submission.
Enter the ID. Use the List all forms in the workspace source template to find it.
Gist destinations can also be manually configured to send data to any valid Gist API endpoint. You can also configure Nexla to send the response that Gist returns after each call to a new Nexla webhook data source, for example to capture the Gist-assigned id of each created record. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The Gist API accepts JSON request bodies. Check the Gist API reference for the method each operation needs: several updates use POST rather than PATCH, for example renaming a tag or updating a collection.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Gist endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Gist until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.