Smileback icon

Smileback

Consume Smileback API using the OpenAPI schema

Actions10

  • Review Actions
  • NPS Response Actions
  • Project Survey Actions
  • CSAT Agents Actions
  • CSAT Boards Actions
  • CSAT Companies Actions
  • CSAT Contacts Actions
  • NPS Campaigns Actions
  • Project Surveys Actions

Overview

This node integrates with the Smileback API to synchronize data related to various resources, including NPS (Net Promoter Score) responses. Specifically, for the "NPS Response" resource and the "Sync" operation, it retrieves NPS response records from the Smileback service. It supports fetching records modified since a specified date and time, enabling incremental synchronization.

Common scenarios where this node is beneficial include:

  • Importing recent NPS feedback into a CRM or analytics platform.
  • Keeping local databases up-to-date with the latest customer satisfaction data.
  • Automating reporting workflows based on fresh NPS responses.

For example, a user can configure the node to fetch all NPS responses modified after a certain date, ensuring only new or updated feedback is processed downstream.

Properties

Name Meaning
Last Modified Since Retrieve records modified after this date and time. This filters the results to recent changes.

Output

The node outputs an array of items, each containing a json field representing a single NPS response record retrieved from the Smileback API. Each JSON object corresponds to one NPS response with its associated data fields as provided by the API.

If the requested resource is not supported, the output will contain a JSON object with a message indicating that the resource is unsupported.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Smileback API. This includes username, password, client ID, and client secret.
  • The node makes HTTP requests to the Smileback API endpoints.
  • Proper configuration of these credentials in n8n is necessary for successful execution.

Troubleshooting

  • Authentication errors: If the node fails to obtain an access token, verify that the API credentials (username, password, client ID, client secret) are correct and have sufficient permissions.
  • Resource not supported: If the node outputs a message stating the resource is not supported, ensure that the "Resource" parameter is set correctly to "NPS Response" for this operation.
  • Rate limiting or API errors: The node uses pagination and waits briefly between requests; however, if the API rate limits are exceeded, consider adjusting request frequency or checking API usage policies.
  • Invalid date format: Ensure the "Last Modified Since" property is set to a valid date-time string; otherwise, the filter may not work as expected.

Links and References

Discussion