Skip to main content

Keap Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Keap location.
keap.png

Keap

Create a Keap Destination​

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

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

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

    Keap destinations can also be configured manually, allowing you to send data to Keap 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 Keap endpoints. Each template is designed specifically for the corresponding Keap 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.

    Create Contact

    Create Contact

    • This endpoint automatically creates contacts in your Keap account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://api.infusionsoft.com/crm/rest/v2/contacts to create contacts. The endpoint URL is automatically constructed based on the Keap REST API base URL.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the contact data to create.
    • Batch mode is disabled by default for this endpoint, which means each record from your Nexset will be sent as a separate API request. This ensures that each contact is created individually.
    • This endpoint does not automatically create a data source to track the responses received from the Keap REST API after each call.

    The request body must be properly formatted JSON that matches the Keap REST API specification for creating contacts. The endpoint requires API key authentication via the X-Keap-API-Key header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. The request body must contain the required fields for contact creation, such as email address, name, and other contact information. For detailed information about creating contacts, including required fields, field names, and request formats, see the Keap REST API documentation.

    Create Company

    Create Company

    • This endpoint automatically creates companies in your Keap account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://api.infusionsoft.com/crm/rest/v2/companies to create companies. The endpoint URL is automatically constructed based on the Keap REST API base URL.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the company data to create.
    • Batch mode is disabled by default for this endpoint, which means each record from your Nexset will be sent as a separate API request. This ensures that each company is created individually.
    • This endpoint does not automatically create a data source to track the responses received from the Keap REST API after each call.

    The request body must be properly formatted JSON that matches the Keap REST API specification for creating companies. The endpoint requires API key authentication via the X-Keap-API-Key header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. The request body must contain the required fields for company creation, such as company name and other company information. For detailed information about creating companies, including required fields, field names, and request formats, see the Keap REST API documentation.

Configure Manually​

Keap destinations can be manually configured to send data to any valid Keap REST 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 Keap destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format​

  1. Select the format in which the Nexset data will be sent to the Keap REST API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Keap REST API typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Keap REST API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Keap REST API endpoints typically follow the pattern https://api.infusionsoft.com/crm/rest/v2/{endpoint_path}.

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. The endpoint requires API key authentication via the X-Keap-API-Key header, which is handled automatically by your credential configuration. The API key is sent in the X-Keap-API-Key header for all API requests to the Keap REST API. For detailed information about Keap REST API endpoints, authentication, and available APIs, see the Keap Developer Guide.