ConvertKit (now Kit) is an email marketing and audience management platform built for creators, offering customizable forms and landing pages to grow subscribers, audience tagging and segmentation, automated email sequences and broadcasts, and tools to sell digital products and paid newsletter subscriptions.
Power end-to-end data operations for your ConvertKit API with Nexla. Our bi-directional ConvertKit connector is purpose-built for ConvertKit, 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 ConvertKit or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ConvertKit 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
Before creating a ConvertKit credential, you need to obtain an API Secret Key from your ConvertKit account. The API Secret Key is required to authenticate with the ConvertKit API v3.
To obtain your API Secret Key, you need to have a ConvertKit account with API access enabled. Once you have access to your account, you can generate an API Secret Key from the advanced account settings. The API Secret Key grants access to sensitive data and actions on your subscribers. The API Secret Key is sent as the api_secret query parameter to authenticate all API requests to the ConvertKit API v3. For detailed information about API key setup and authentication, refer to the ConvertKit API documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – ConvertKit
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your ConvertKit API Secret Key in the API Secret Key field. This is the API Secret Key you obtained from your ConvertKit advanced account settings. The API Secret Key is sent as the api_secret query parameter to authenticate all API requests to the ConvertKit API v3.
Keep your API Secret Key secure and do not share it publicly. The API Secret Key provides access to sensitive data and actions on your subscribers and should be treated as sensitive information. The API Secret Key is sent as the api_secret query parameter for all API requests to the ConvertKit API v3. For detailed information about obtaining and managing API keys, see the ConvertKit API documentation.
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.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the ConvertKit connector tile, then select the credential that will be used to connect to the ConvertKit instance, and click Next; or, create a new ConvertKit 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 ConvertKit 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.
List resources
This endpoint lists all resources in the creator account. Use this endpoint when you need to access resource information, such as forms, sequences, tags, or other resources in your ConvertKit account.
Enter the resource type you want to retrieve in the Resource Type field. This should be the type of resource you want to list (e.g., forms, sequences, tags, subscribers). The resource type determines which resources will be retrieved.
The endpoint uses GET requests to https://api.convertkit.com/v3/{'{resource_type}'}?api_secret={'{api_secret}'} where {resource_type} is the resource type you provide and {api_secret} is your API Secret Key from the credential configuration. The endpoint URL is automatically constructed based on the ConvertKit API base URL, the resource type, and your credential's API Secret Key.
The endpoint does not use pagination and returns all resources of the specified type in a single request.
The endpoint will return all resources of the specified type. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.
Resource types should match the ConvertKit API v3 specification. Common resource types include forms, sequences, tags, subscribers, and account. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. You can use the advanced tab for fetching a filtered list of resources. For detailed information about listing resources, see the ConvertKit API documentation.
Get Statistics
This endpoint gets statistics for a specific broadcast. Use this endpoint when you need to access broadcast performance metrics, engagement statistics, or analytics data for a specific broadcast in your ConvertKit account.
Enter the broadcast ID for which you want to retrieve statistics in the Broadcast ID field. This is the unique identifier of the broadcast for which you want to get statistics.
The endpoint uses GET requests to https://api.convertkit.com/v3/broadcasts/{'{broadcast_id}'}/stats?api_secret={'{api_secret}'} where {broadcast_id} is the broadcast ID you provide and {api_secret} is your API Secret Key from the credential configuration. The endpoint URL is automatically constructed based on the ConvertKit API base URL, the broadcast ID, and your credential's API Secret Key.
The endpoint does not use pagination and returns the complete broadcast statistics in a single request.
The endpoint will return statistics for the specified broadcast. The response data is extracted from the broadcast array in the API response ($.broadcast[*]), with each statistic record processed individually.
Broadcast IDs can be obtained from other ConvertKit API endpoints, such as the List resources endpoint by selecting broadcasts as the resource type, which returns all broadcasts with their corresponding IDs. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $.broadcast[*], which extracts all items from the broadcast array in the API response. For detailed information about getting broadcast statistics, see the ConvertKit API documentation.
List subscriptions
This endpoint lists subscriptions to a resource including subscriber data. Use this endpoint when you need to access subscription information, subscriber details, or subscription data for a specific resource (form, sequence, or tag) in your ConvertKit account.
Enter the resource type in the Resource Type field. This should be the type of resource for which you want to list subscriptions (e.g., forms, sequences, tags).
Enter the resource ID in the Resource ID field. This is the unique identifier of the specific resource (form, sequence, or tag) for which you want to list subscriptions.
The endpoint uses GET requests to https://api.convertkit.com/v3/{'{resource_type}'}/{'{resource_id}'}/subscriptions?api_secret={'{api_secret}'} where {resource_type} is the resource type, {resource_id} is the resource ID you provide, and {api_secret} is your API Secret Key from the credential configuration. The endpoint URL is automatically constructed based on the ConvertKit API base URL, the resource type and ID, and your credential's API Secret Key.
The endpoint does not use pagination and returns all subscriptions for the specified resource in a single request.
The endpoint will return all subscriptions to the specified resource, including subscriber data. The response data is extracted from the subscriptions array in the API response ($.subscriptions[*]), with each subscription record processed individually.
Resource IDs can be obtained from the List resources endpoint by selecting the appropriate resource type, which returns all resources with their corresponding IDs. The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $.subscriptions[*], which extracts all items from the subscriptions array in the API response. For detailed information about listing subscriptions, see the ConvertKit API documentation.
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.
ConvertKit data sources can also be manually configured to ingest data from any valid ConvertKit API v3 endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. 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.
ConvertKit API v3 endpoint URLs typically follow the pattern https://api.convertkit.com/v3/{'{endpoint_path}'}. Remember to include the api_secret query parameter with your API Secret Key on every request. For detailed information about ConvertKit API endpoints, see the ConvertKit API documentation.
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 ConvertKit 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 ConvertKit destination, and select the Send to Destination option from the menu. Select the ConvertKit connector from the list of available destination connectors, then select the credential that will be used to connect to the ConvertKit organization, and click Next; or, create a new ConvertKit credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common ConvertKit 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.
Add subscriber
This endpoint subscribes an email address to the resource. Use this endpoint when you need to add subscribers to forms, sequences, or tags from your data sources.
Enter the resource type in the Resource Type field. This should be the type of resource to which you want to subscribe the email address (e.g., forms, sequences, tags).
Enter the resource ID in the Resource ID field. This is the unique identifier of the specific resource (form, sequence, or tag) to which you want to subscribe the email address.
The endpoint uses POST requests to https://api.convertkit.com/v3/{'{resource_type}'}/{'{resource_id}'}/subscribe?api_secret={'{api_secret}'} where {resource_type} is the resource type, {resource_id} is the resource ID you provide, and {api_secret} is your API Secret Key from the credential configuration. The endpoint URL is automatically constructed based on the ConvertKit API base URL, the resource type and ID, and your credential's API Secret Key.
The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the subscriber data to add. The request body should follow the ConvertKit API v3 specification for adding subscribers, including required fields and field names.
Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to add a subscriber. If you need to add multiple subscribers, you can send multiple records, but each will be processed as a separate request.
Resource IDs can be obtained from the "List resources" data source endpoint by selecting the appropriate resource type, which returns all resources with their corresponding IDs. The request body must be properly formatted JSON that matches the ConvertKit API v3 specification for adding subscribers. The endpoint requires API Secret Key authentication via the api_secret query parameter, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about adding subscribers, including required fields, field names, and request formats, see the ConvertKit API documentation.
Create a resource
This endpoint creates resources such as a broadcast or a webhook to send events. Use this endpoint when you need to create new resources in your ConvertKit account from your data sources.
Enter the resource type you want to create in the Resource Type field. This should be the type of resource you want to create (e.g., broadcasts, webhooks). The resource type determines which resource will be created.
The endpoint uses POST requests to https://api.convertkit.com/v3/{'{resource_type}'}?api_secret={'{api_secret}'} where {resource_type} is the resource type you provide and {api_secret} is your API Secret Key from the credential configuration. The endpoint URL is automatically constructed based on the ConvertKit API base URL, the resource type, and your credential's API Secret Key.
The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the resource data to create. The request body should follow the ConvertKit API v3 specification for creating resources, including required fields and field names.
Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a resource. If you need to create multiple resources, you can send multiple records, but each will be processed as a separate request.
Resource types should match the ConvertKit API v3 specification. Common resource types include broadcasts and webhooks. The request body must be properly formatted JSON that matches the ConvertKit API v3 specification for creating resources. The endpoint requires API Secret Key authentication via the api_secret query parameter, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating resources, including required fields, field names, and request formats, see the ConvertKit API documentation.
ConvertKit destinations can also be manually configured to send data to any valid ConvertKit API v3 endpoint. 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.
ConvertKit API v3 endpoint URLs typically follow the pattern https://api.convertkit.com/v3/{'{endpoint_path}'}, and primarily use POST for data-writing operations with a JSON request body. Remember to include the api_secret query parameter with your API Secret Key on every request; the Content-Type: application/json header is included automatically.
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 ConvertKit endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the ConvertKit endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
