Delighted
Overview
Birdie allows you to automatically ingest responses from your Delighted surveys into your workspace, enabling deeper analysis and insight generation through our VoC intelligence platform. This integration captures not only survey answers but also associated metadata like respondent, company, and channel information.
With this integration, you’ll be able to:
Import NPS/CSAT survey responses from Delighted
Capture associated metadata (e.g., user info, company, timestamps, tags)
Automatically sync data into Birdie for analysis
Below is a step-by-step guide to help you set up your Delighted → Birdie integration using the Delighted REST API.
Requirements
Birdie's integration with Delighted requires the API token for your project. Delighted works as a platform where you can create multiple projects. Each project corresponds to a survey, and Birdie needs the API token associated with the specific project you want to integrate.
Get Your Delighted API Key
Delighted requires a private API key to authenticate API requests.
Log in to your Delighted account and select the correct project (top left corner).
Go to Settings > API to find your private key.
If you don’t have access, ask your Delighted admin to retrieve it for you.
Once you get access to your API key, share it securely with the Birdie team: https://onetimesecret.com/en/
Your API key is sensitive. Never share it publicly. It will be used via HTTP Basic Authentication as the username, leaving the password field blank.
Connect to Birdie
After completing the setup above and sharing your Delighted API key securely, the Birdie team will configure the connector and confirm when the integration is active.
Data in scope
Delighted → Birdie integration imports:
NPS/CSAT survey responses from the connected Delighted project
Response metadata such as respondent, company, timestamps, tags and custom fields (when configured)
These responses are synchronized on a regular schedule so that the latest interactions and content are consistently reflected in Birdie.
Rate Limiting Considerations
Delighted enforces rate limiting in rare cases (bulk data fetch or faulty retry loops). If this happens:
You’ll receive a 429 Too Many Requests error.
Birdie will handle this automatically with exponential backoff.
Alternatively, Delighted may provide a Retry-After header.
You don’t need to take action unless the rate limit persists.
Import Process and Update Frequency
Birdie imports the most recently updated survey responses from Delighted and then retrieves their metadata. This process runs on a regular schedule, ensuring that the latest interactions and content are consistently reflected in the application.
Custom Fields
If your Delighted setup includes custom fields for survey responses, these fields can be mapped directly into Birdie, preserving your unique data structure. For survey responses, the data follows this response pattern: https://app.delighted.com/docs/api/listing-survey-responses
Once imported, Delighted custom fields appear as Birdie custom fields, maintaining consistency across both platforms. Mapped to Birdie’s data structure, these fields enhance data organization and filtering, supporting extended segmentation within Birdie’s interface. This allows for customized workflows and data displays based on the unique attributes of each survey response.
If you need further help, contact your Birdie representative or Delighted admin for project-specific assistance.
Last updated