Skip to main content

Delighted Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a sync or streaming data flow that sends data to a Delighted location.
delighted_api.png

Delighted

Create a Delighted Destination​

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

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

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

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

    Unsubscribe people

    This endpoint adds a person to the user's unsubscribe list. Use this endpoint when you need to unsubscribe people from surveys or remove them from your mailing list in your Delighted account from your data sources.

    • This endpoint automatically unsubscribes people from your Delighted account. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://api.delighted.com/v1/unsubscribes.json. The endpoint URL is automatically constructed based on the Delighted API base URL.
    • 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 unsubscribe data. The request body should follow the Delighted API specification for unsubscribing people, 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 unsubscribe a person. If you need to unsubscribe multiple people, you can send multiple records, but each will be processed as a separate request.
    • This endpoint automatically creates a data source to track the responses received from the Delighted API after each call.

    The request body must be properly formatted JSON that matches the Delighted API specification for unsubscribing people. The endpoint requires Basic Authentication with your API key as the username, 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. This endpoint automatically creates a data source (create.datasource: true) to track responses. For detailed information about unsubscribing people, including required fields, field names, and request formats, see the Delighted API documentation.

    Schedule a survey

    This endpoint creates or updates a person and schedules a survey email. Use this endpoint when you need to create or update people in your Delighted account and send them survey emails from your data sources.

    • This endpoint automatically creates or updates people and schedules survey emails in your Delighted account. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://api.delighted.com/v1/people.json. The endpoint URL is automatically constructed based on the Delighted API base URL.
    • 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 person data and survey scheduling information. The request body should follow the Delighted API specification for sending to people, 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 or update a person and schedule a survey. If you need to schedule surveys for multiple people, you can send multiple records, but each will be processed as a separate request.
    • This endpoint automatically creates a data source to track the responses received from the Delighted API after each call.

    The request body must be properly formatted JSON that matches the Delighted API specification for sending to people. The endpoint requires Basic Authentication with your API key as the username, 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. This endpoint automatically creates a data source (create.datasource: true) to track responses. For detailed information about sending to people and scheduling surveys, including required fields, field names, and request formats, see the Delighted API documentation.

    Delete people By email address

    This endpoint deletes people by email and all information related to them. Use this endpoint when you need to delete people from your Delighted account by their email address from your data sources.

    • Enter the dataset attribute that corresponds to the email address that must be deleted in the Email address dataset attribute field. This should be the name of the attribute in your Nexset that contains the email address of the person you want to delete.

    • The endpoint uses POST requests to https://api.delighted.com/v1/people.json/email:{email} where {email} is the email address from the dataset attribute you specify. The endpoint URL is automatically constructed based on the Delighted API base URL and the email address from your Nexset data.
    • 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 any additional deletion data. The request body should follow the Delighted API specification for deleting people, 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 delete a person. If you need to delete multiple people, you can send multiple records, but each will be processed as a separate request.
    • This endpoint automatically creates a data source to track the responses received from the Delighted API after each call.

    The email address dataset attribute should match the name of the attribute in your Nexset that contains the email address. The endpoint uses the email address from your Nexset data to construct the URL path. The request body must be properly formatted JSON that matches the Delighted API specification for deleting people. The endpoint requires Basic Authentication with your API key as the username, 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. This endpoint automatically creates a data source (create.datasource: true) to track responses. For detailed information about deleting people, including required fields, field names, and request formats, see the Delighted API documentation.

Configure Manually​

Delighted destinations can be manually configured to send data to any valid Delighted 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 Delighted 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 Delighted API from the Method pulldown menu. The Delighted API primarily uses POST requests for data writing operations. The most common methods are:

    • POST: For creating new resources or performing actions (e.g., unsubscribing people, scheduling surveys, deleting people)
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

Data Format​

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

API Endpoint URL​

  1. Enter the URL of the Delighted 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. Delighted API endpoints typically follow the pattern https://api.delighted.com/v1/{endpoint_path}.json.

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 Basic Authentication with your API key as the username, which is handled automatically by your credential configuration. For detailed information about Delighted API endpoints and available APIs, see the Delighted API documentation.

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). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration. The Delighted API requires Basic Authentication with your API key as the username, which is handled automatically by your credential configuration. The Content-Type: application/json header is typically set automatically for JSON request bodies.

Request Body​

Optional

  • If the API endpoint requires a specific request body format, configure how Nexla should format the request body from your Nexset data. The request body can be sent as JSON, XML, or form data, depending on the API endpoint requirements.

    • For JSON format, select JSON from the Request Body Format dropdown, and the Nexset data will be sent as a JSON object in the request body. Delighted API endpoints typically use JSON format for request bodies.

    • For XML format, select XML from the Request Body Format dropdown, and the Nexset data will be converted to XML format in the request body.

    • For Form data format, select Form Data from the Request Body Format dropdown, and the Nexset data will be sent as form-encoded data in the request body.

Save the Destination​

  1. Once all configuration steps have been completed, click the Save button to save your destination configuration.

  2. The destination will now be available in your data flow and will begin sending data to the Delighted endpoint according to the configured settings.