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 from various Smileback resources, including CSAT Boards. It fetches records from the selected resource, optionally filtered by a "Last Modified Since" date/time, enabling users to keep their local data up-to-date with changes in Smileback.

A common use case is syncing customer satisfaction (CSAT) board data into a CRM or analytics platform to analyze customer feedback trends over time. For example, a user might schedule this node to run daily, retrieving all CSAT boards updated since the last sync, ensuring only new or changed data is processed.

Properties

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

Output

The node outputs an array of JSON objects, each representing a record retrieved from the Smileback API for the specified resource. Each item corresponds to one entity (e.g., one CSAT Board) with its full data as returned by the API.

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

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Smileback API.
  • The node performs OAuth2 password grant authentication using username, password, client ID, and client secret credentials.
  • The base URL for the Smileback API is configurable via the credentials.
  • The node uses the Smileback API v3 endpoints.

Troubleshooting

  • Authentication errors: If the node fails to obtain an access token, verify that the provided API credentials (username, password, client ID, client secret) are correct and have the necessary permissions.
  • Unsupported resource error: If you select a resource not implemented in the node, the output will indicate "Resource not supported." Ensure you choose a valid resource name.
  • Rate limiting or API errors: The node includes a small delay between paginated requests to avoid hitting rate limits. If you encounter errors related to request limits, consider increasing delays or reducing request frequency.
  • Empty results: If no data is returned, check the "Last Modified Since" filter; it may be too restrictive or incorrectly formatted.

Links and References

Discussion