Skip to main content

Custify Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Custify location.
custify_api_destination.png

Custify

Create a Custify Destination​

  1. Click the + icon on the Nexset that will be sent to the Custify destination, and select the Send to Destination option from the menu.

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

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

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

Configure Using a Template​

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

  • To configure this destination using a template, 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.

    Upsert Person

    Creates or updates a person (contact) record in Custify. If a person with the same user_id or email already exists in Custify, that record will be updated; otherwise, a new person record will be created. Use this endpoint to sync contact data from your CRM, data warehouse, or product database into Custify.

    • Map your Nexset fields to the Custify person object fields. At minimum, include one of the following fields to allow Custify to match existing records:

      • user_id: Your internal unique identifier for the user. This is the primary match key used by Custify for upsert operations.
      • email: The person's email address, used as a secondary match key if user_id is not provided.
    • Additional person fields you can include in the payload are: name, phone, signed_up_at, churned_at, plan, company_id, and any custom attributes defined in your Custify account.

    Custify will automatically create or update the record based on the match key. For complete information about the people upsert API and accepted fields, refer to the Custify API documentation.

    Upsert Company

    Creates or updates a company (account) record in Custify. If a company with the matching company_id already exists, it will be updated; otherwise, a new company record will be created. Use this endpoint to sync account data from your CRM, billing system, or data warehouse into Custify to keep company health data current.

    • Map your Nexset fields to the Custify company object fields. The following field is required for matching:

      • company_id: Your internal unique identifier for the company. Custify uses this as the primary match key for upsert operations.
    • Additional company fields you can include are: name, website, plan, size, mrr, churned_at, signed_up_at, industry, and any custom attributes defined in your Custify account.

    Custom company attributes configured in your Custify account can also be included in the payload. For complete information about accepted fields, refer to the Custify API documentation.

    Upsert Subscription

    Creates or updates a subscription record for a company in Custify, including plan details, MRR, and renewal dates. Use this endpoint to sync subscription and billing data from your payment processor or billing system into Custify to power revenue-based health scores and churn risk analysis.

    • Map your Nexset fields to the Custify subscription object fields. Key fields include:

      • company_id: The unique identifier of the company this subscription belongs to.
      • plan: The name of the subscription plan.
      • mrr: Monthly recurring revenue for this subscription.
      • start_date: The subscription start date in ISO 8601 format.
      • renewal_date: The upcoming renewal date in ISO 8601 format.
      • status: The subscription status (e.g., active, canceled, trialing).

    Keeping subscription data current in Custify is essential for accurate MRR-based health scores and churn risk detection. For complete information about accepted subscription fields, refer to the Custify API documentation.

    Upsert Invoice

    Creates or updates an invoice record in Custify for a company. Use this endpoint to sync invoice and payment data from your billing system into Custify to provide customer success managers with a complete financial picture of each account.

    • Map your Nexset fields to the Custify invoice object fields. Key fields include:

      • company_id: The unique identifier of the company associated with this invoice.
      • amount: The invoice amount.
      • status: The invoice status (e.g., paid, pending, overdue).
      • due_date: The invoice due date in ISO 8601 format.

    For complete information about accepted invoice fields, refer to the Custify API documentation.

    Upsert Deal

    Creates or updates a deal record in Custify with stage, value, and company associations. Use this endpoint to sync expansion or upsell opportunity data from your CRM into Custify, enabling customer success managers to track and act on revenue opportunities from within the platform.

    • Map your Nexset fields to the Custify deal object fields. Key fields include:

      • company_id: The unique identifier of the company associated with this deal.
      • name: The deal name or title.
      • stage: The current stage of the deal in your pipeline.
      • value: The monetary value of the deal.
      • close_date: The expected or actual close date in ISO 8601 format.

    For complete information about accepted deal fields, refer to the Custify API documentation.

    Insert Event

    Sends a product usage or behavioral event to Custify tied to a specific user and company. Events are used by Custify to calculate health scores and trigger automated playbooks based on customer activity signals. Use this endpoint to stream product usage data, feature adoption events, or any custom behavioral signals from your application into Custify.

    • Map your Nexset fields to the Custify event object. Key fields include:

      • user_id: The unique identifier of the user who performed the event. Must match the user_id of an existing person in Custify.
      • company_id: The unique identifier of the company associated with the event.
      • name: The name of the event (e.g., feature_used, login, export_completed).
      • created_at: The timestamp when the event occurred, in ISO 8601 format.
    • Custom event properties can also be included as additional key-value pairs in the payload, allowing you to pass context such as feature names, plan tiers, or usage counts alongside each event.

    Events are the primary signal used by Custify to compute health scores and trigger playbooks. For complete information about the event schema and accepted fields, refer to the Custify API documentation.

    Create Task

    Creates a task in Custify with an assignee, due date, and a link to a company or person. Use this endpoint to automatically generate customer success tasks from external triggers—for example, creating a follow-up task when a health score drops below a threshold or when a renewal date is approaching.

    • Map your Nexset fields to the Custify task object. Key fields include:

      • name: The task title or description.
      • due_date: The task due date in ISO 8601 format.
      • assignee_email: The email address of the Custify user to whom the task should be assigned.
      • company_id: The unique identifier of the company linked to this task.
      • person_id: The unique identifier of the person linked to this task (optional).

    For complete information about accepted task fields, refer to the Custify API documentation.

    Create Note

    Creates a note in Custify linked to a company or person. Use this endpoint to automatically log AI-generated call summaries, meeting transcripts, support ticket summaries, or other free-text observations into Custify so customer success managers always have context on customer interactions.

    • Map your Nexset fields to the Custify note object. Key fields include:

      • text: The content of the note.
      • company_id: The unique identifier of the company to which this note should be linked.
      • person_id: The unique identifier of the person to which this note should be linked (optional).
      • created_at: The timestamp for the note in ISO 8601 format.

    Notes created via the API will appear in the company or person's activity timeline within Custify. For complete information about accepted note fields, refer to the Custify API documentation.

    Upsert Custom Data Object

    Adds or updates a custom data object in Custify. Custom data objects allow you to store structured, domain-specific data beyond the standard Custify schema—such as AI feature usage metrics, product KPIs, or industry-specific measurements—and surface that data in health scores and customer profiles.

    • Map your Nexset fields to the Custify custom object schema. The payload structure depends on the custom object type configured in your Custify account. Typically, the payload includes:

      • type: The name/type of the custom data object as configured in Custify.
      • company_id: The unique identifier of the associated company.
      • Any custom fields defined for the object type in your Custify account configuration.

    Custom data object schemas must be defined in your Custify account before data can be written to them. For complete information about custom data objects and accepted fields, refer to the Custify API documentation.

    Send Batch Request

    Sends multiple Custify API operations in a single batch request, supporting bulk upserts for people and companies. Use this endpoint when you need to efficiently load large volumes of person or company records into Custify in a single operation, reducing the number of API calls required.

    • This endpoint uses Custify's batch API at https://app.custify.com/api/batch, which accepts up to 500 records per request. Nexla will automatically chunk your data into batches of up to 500 records.

    • Each item in the batch payload should be a valid Custify API operation object. For example, to batch-upsert people, each item should follow the same schema as a single person upsert. Key fields per record include:

      • user_id or email: The match key used to identify existing records for upsert operations.
      • Any additional person or company fields appropriate for the batch operation type.

    The batch endpoint is the recommended approach for initial data loads or large-scale synchronization jobs. For complete information about the Custify batch API and supported operation types, refer to the Custify API documentation.

Configure Manually​

Custify destinations can be manually configured to send data to any valid Custify API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Custify API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, 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. Most Custify write operations use POST for creates and upserts.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Custify API from the Content Format pulldown menu. Custify's REST API accepts JSON format for all write operations. Nexla will automatically convert the data to JSON for each API call.

API Endpoint URL​

  1. Enter the URL of the Custify API endpoint to which you want to send the Nexset data in the URL field. All Custify API write endpoints use the base URL https://app.custify.com/api/ followed by the resource path. For example:
    • https://app.custify.com/api/people — upsert a person
    • https://app.custify.com/api/company — upsert a company
    • https://app.custify.com/api/event — insert an event
    • https://app.custify.com/api/note — create a note
    • https://app.custify.com/api/batch — send a batch of operations

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, 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.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Custify destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100. For the Custify batch endpoint (/api/batch), the maximum batch size is 500 records.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Property Inside JSON Object

  1. Enter the name of the JSON property that should contain the batched records in the Property Name field. For Custify's batch API, use batch as the property name.
  2. If any additional properties should be included in the request, enter the properties in the Other Props field in JSON format.

Code

  1. Enter the code that will be used to create the batched request in the code editor below the Grouping Algorithm field.

Response Webhook​

Optional

Nexla can automatically send the response received from the Custify API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Custify API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Custify API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Custify API using the current settings.

Save & Activate the Destination​

  • 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 begin sending data to Custify, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Custify until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.