Custify Data Source

The Custify connector enables you to ingest customer success data—including people, companies, subscriptions, deals, tasks, notes, tickets, and more—from your Custify account into Nexla data flows. Follow the instructions below to create a new data flow that ingests data from a Custify source in Nexla.

Custify

Create a New Data Flow

1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

2. Select the Custify connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Custify instance, and click Next; or, create a new Custify credential for use in this flow.

3. In Nexla, Custify data sources can be created using pre-built endpoint templates, which expedite source setup for common Custify endpoints. Each template is designed specifically for the corresponding Custify endpoint, making source configuration easy and efficient.
   • To configure this source using a template, follow the instructions in Configure Using a Template.

   Custify sources can also be configured manually, allowing you to ingest data from Custify endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
   • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Custify endpoints. Each template is designed specifically for the corresponding Custify endpoint, making data source setup easy and efficient.

Endpoint Settings

• 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Get People

Retrieves all people (contacts/users) from your Custify account. Use this endpoint to pull your full contact list for analysis, enrichment, or syncing to downstream systems. Supports filtering by email, company, or last-updated date.

• Optionally, configure the following endpoint settings to control what data is retrieved:

  • Page Size: Enter the number of people records to fetch per page. The maximum value is 100, and the default is 100. Reducing this value can help in environments with strict rate limits.
  • Updated After: Enter an ISO 8601 date and time to filter results to only people updated after that point (for example, 2024-01-01T00:00:00Z). By default, Nexla uses the macro {now-30} to retrieve records updated in the last 30 days, enabling incremental data ingestion on each run.

The Offset parameter is managed automatically by Nexla to handle pagination across large datasets. You do not need to configure it manually. For complete information about the People API, refer to the Custify API documentation.

Get Person by ID

Retrieves a single person record from Custify by their unique Custify person ID. Use this endpoint when you need to pull detailed profile data for a specific contact rather than fetching your entire contact list.

• Person ID (required): Enter the unique Custify ID of the person you want to retrieve. Custify person IDs can be found in the URL when viewing a person's profile in the Custify app, or in the id field of records returned by the Get People endpoint. This field is required.

This endpoint returns a single record rather than a paginated list. For retrieving all people or filtering by date, use the Get People endpoint instead.

Get Companies

Retrieves all companies from your Custify account, including health scores, lifecycle stage, MRR, and custom attributes. Use this endpoint to analyze your company portfolio, segment accounts, or sync company data to external analytics or CRM tools.

• Optionally, configure the following endpoint settings to control what data is retrieved:

  • Page Size: Enter the number of company records to fetch per page. The maximum value is 100, and the default is 100.
  • Updated After: Enter an ISO 8601 date and time to filter results to only companies updated after that point (for example, 2024-01-01T00:00:00Z). By default, Nexla uses the macro {now-30} to retrieve records updated in the last 30 days, enabling incremental ingestion on each run.

Pagination is managed automatically by Nexla. For complete information about the Company API, refer to the Custify API documentation.

Get Company by ID

Retrieves a single company record from Custify by its unique company ID. Use this endpoint when you need complete details for a specific account rather than retrieving your full company list.

• Company ID (required): Enter the unique Custify company_id of the company you want to retrieve. Company IDs can be found in the Custify app on the company's detail page, or in the company_id field of records returned by the Get Companies endpoint. This field is required.

Get Company People

Lists all people (contacts) associated with a specific company in Custify. Use this endpoint to retrieve the full contact roster for an account, which is useful for account-level reporting or targeted outreach workflows.

• Company ID (required): Enter the unique Custify company_id of the company whose associated people you want to list. This field is required.

This endpoint returns all people linked to the specified company. To retrieve people across all companies, use the Get People endpoint instead.

Get Subscriptions

Retrieves all subscriptions from your Custify account, including MRR, plan name, subscription status, and renewal dates. Use this endpoint to analyze revenue data, track churn risk by subscription, or sync billing information to downstream systems.

• Optionally, configure the following endpoint settings:

  • Page Size: Enter the number of subscription records to fetch per page. The maximum value is 100, and the default is 100.

Pagination is managed automatically by Nexla. For complete information about the Subscription API, refer to the Custify API documentation.

Get Invoices

Retrieves all invoices from your Custify account, including amount, status, due date, and associated company. Use this endpoint to analyze billing history, track outstanding payments, or reconcile invoice data with external financial systems.

• Optionally, configure the following endpoint settings:

  • Page Size: Enter the number of invoice records to fetch per page. The maximum value is 100, and the default is 100.

Pagination is managed automatically by Nexla. For complete information about the Invoice API, refer to the Custify API documentation.

Get Deals

Retrieves all deals from your Custify account, including deal stage, value, expected close date, and associated company. Use this endpoint to track expansion opportunities, analyze deal pipeline data, or sync deal information to a CRM or reporting tool.

• Optionally, configure the following endpoint settings:

  • Page Size: Enter the number of deal records to fetch per page. The maximum value is 100, and the default is 100.

Pagination is managed automatically by Nexla. For complete information about the Deal API, refer to the Custify API documentation.

Get Tasks

Retrieves all tasks from your Custify account, including assignee, due date, status, and the linked company or person. Use this endpoint to monitor team workloads, track open action items, or integrate task data with project management tools.

• Optionally, configure the following endpoint settings:

  • Page Size: Enter the number of task records to fetch per page. The maximum value is 100, and the default is 100.

Pagination is managed automatically by Nexla. For complete information about the Task API, refer to the Custify API documentation.

Get Notes

Retrieves all notes from your Custify account associated with companies or people. Use this endpoint to export call summaries, meeting notes, or other free-text observations logged by your customer success team.

• Optionally, configure the following endpoint settings:

  • Page Size: Enter the number of note records to fetch per page. The maximum value is 100, and the default is 100.

Pagination is managed automatically by Nexla. For complete information about the Note API, refer to the Custify API documentation.

Get Tags

Retrieves all tags defined in your Custify account. Tags are used in Custify to segment and categorize people and companies, enabling targeted playbooks and filtered views. Use this endpoint to export your tag taxonomy for use in reporting or segmentation pipelines.

• No additional configuration is required for this endpoint. Nexla will retrieve all tags available in your Custify account.

Get Tickets

Retrieves support tickets from your Custify account linked to companies or people. Use this endpoint to analyze support volume, track ticket resolution data, or integrate Custify ticket data with external helpdesk reporting tools.

• Optionally, configure the following endpoint settings:

  • Page Size: Enter the number of ticket records to fetch per page. The maximum value is 100, and the default is 100.

Pagination is managed automatically by Nexla. For complete information about the Ticket API, refer to the Custify API documentation.

Get Comments

Retrieves all comments from your Custify account associated with notes or tickets. Use this endpoint to capture the full conversation thread on customer interactions for analysis or archival purposes.

• Optionally, configure the following endpoint settings:

  • Page Size: Enter the number of comment records to fetch per page. The maximum value is 100, and the default is 100.

Pagination is managed automatically by Nexla. For complete information about the Comment API, refer to the Custify API documentation.

Endpoint Testing

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

• To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

• If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually

Custify data sources can be manually configured to ingest data from any valid Custify API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Custify sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.

API Method

1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

2. Select the API method that will be used for calls to the Custify API from the Method pulldown menu. The most common method for Custify data retrieval is:

   • GET: For retrieving data from the API. All Custify read operations use GET requests.
   • POST: For sending data to the API or triggering actions.

API Endpoint URL

3. Enter the URL of the Custify API endpoint from which this source will fetch data in the Set API URL field. All Custify API endpoints use the base URL https://app.custify.com/api/ followed by the resource path. For example:
   • https://app.custify.com/api/people — retrieves all people
   • https://app.custify.com/api/company — retrieves all companies
   • https://app.custify.com/api/subscription — retrieves all subscriptions

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. For a complete list of available Custify API endpoints, refer to the Custify API documentation.

Date/Time Macros (API URL)

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

Date/time macros are particularly useful with Custify's updated_after query parameter, which filters results to records updated after a specific date. For example, appending ?updated_after={'{now-7}'} to the people endpoint URL retrieves only people updated in the last 7 days.

4. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

   • {now} – The current datetime
   • {now-1} – The datetime one time unit before the current datetime
   • {now+1} – The datetime one time unit after the current datetime
   • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-30) to indicate the datetime 30 time units before the current datetime

5. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. Custify's updated_after parameter expects ISO 8601 format (e.g., 2024-01-01T00:00:00Z).

6. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.

Lookup-based macros are useful when you need to pass a Custify company ID or person ID retrieved from another Nexla source directly into the API URL—for example, when fetching people for a specific company using https://app.custify.com/api/company/{'{company_id}'}/people.

7. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

8. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data

Optional

If only a subset of the data returned by the API endpoint is needed, you can designate the part of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. Custify API responses typically return records nested within a named array.

For example, the Custify people endpoint returns a response like {"people": [...], "total": 100}. By specifying $.people[*] as the path to data, Nexla treats each element of the people array as a separate record.

Common Custify response data paths include: $.people[*] for people, $.companies[*] for companies, $.subscriptions[*] for subscriptions, $.deals[*] for deals, $.tasks[*] for tasks, $.notes[*] for notes, $.tickets[*] for tickets, and $.tags[*] for tags.

• To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

  • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.people[*] to access the array of people records within the response object).
  Path to Data Example:

  If the Custify API response contains a top-level array named people that contains the relevant data, the path to the response would be entered as $.people[*].

Autogenerate Path Suggestions

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

• To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

• Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

  

Metadata

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. For Custify responses, this is useful for capturing pagination metadata such as total record counts alongside your data records.

• To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

  • For responses in JSON format, enter the JSON path to the object or array that contains the metadata.

Request Headers

Optional

• If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

  You do not need to include the Authorization header or other headers already present in your Custify credential. Nexla automatically includes the Bearer token authentication header based on your configured credential.

Endpoint Testing

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

• To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

• If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source

1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Custify 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.