Skip to main content

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 SendPulse location.
sendpulse_api.png

Sendpulse

Create a SendPulse Destination​

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

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

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

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

    This endpoint template creates a mailing list in your SendPulse account using records from a Nexset. Use this template when you need to create new mailing lists in your SendPulse account.

    • This endpoint sends data as JSON in the request body to create mailing lists in your SendPulse account. Each record from your Nexset will be sent as a separate API request to create a new mailing list in SendPulse. The request body should contain the mailing list data in the format required by the SendPulse API.

    This endpoint sends data as JSON in the request body to create mailing lists in your SendPulse account. Each record from your Nexset will be sent as a separate API request to create a new mailing list in SendPulse. The request body should contain the mailing list data in the format required by the SendPulse API.

    The mailing list structure must match the SendPulse API's expected format. For detailed information about mailing list creation, request body formats, and available mailing list properties, see the SendPulse API documentation.

    Delete Emails List

    This endpoint template deletes a list of emails from a mailing list in your SendPulse account using records from a Nexset. Use this template when you need to remove emails from a mailing list.

    • Enter the mailing list ID in the ID field. This should be the unique identifier of the mailing list from which you want to delete emails. The mailing list ID determines which mailing list's emails will be deleted.

    This endpoint sends data as JSON in the request body to delete emails from a mailing list in your SendPulse account. Each record from your Nexset will be sent as a separate API request to delete emails from the specified mailing list. The request body should contain the email data in the format required by the SendPulse API.

    For detailed information about email deletion, request body formats, and available email properties, see the SendPulse API documentation.

Configure Manually​

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

Using manual configuration, you can also configure Nexla to automatically send the response received from the SendPulse 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 SendPulse API from the Method pulldown menu. SendPulse API typically uses POST method for creating resources and deleting emails.

Data Format​

  1. Select the format in which the Nexset data will be sent to the SendPulse API from the Content Format pulldown menu. SendPulse API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the SendPulse API endpoint to which data will be sent in the URL field. This should be the complete URL to your SendPulse endpoint (e.g., https://api.sendpulse.com/addressbooks, https://api.sendpulse.com/addressbooks/{id}/emails). Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The SendPulse API endpoint URL should point to the endpoint where you want to create mailing lists or delete emails. The endpoint URL should include the API path (/api.sendpulse.com/) and the resource type path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the SendPulse API. The request body should contain the resource data formatted as JSON, with field names matching the SendPulse API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the SendPulse API's expected format for the specific endpoint you're using. SendPulse API uses specific structures for different endpoints (mailing lists, emails, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the SendPulse API documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.