Smileback

Overview

This node integrates with the Smileback API to synchronize data from various Smileback resources, including NPS Campaigns. It fetches records from the selected resource, optionally filtered by a "Last Modified Since" date, allowing users to retrieve only recently updated data. This is useful for keeping external systems or workflows up-to-date with the latest customer feedback campaigns and related information.

For the NPS Campaigns - Sync operation specifically, the node retrieves NPS campaign records that have been created or modified since a specified date and time. This can help automate reporting, analysis, or further processing of NPS campaigns in other tools.

Practical examples:

• Automatically syncing new or updated NPS campaigns into a CRM or database.
• Triggering follow-up workflows when campaigns are updated.
• Generating reports on recent NPS campaigns without manual export/import.

Properties

Output

The node outputs an array of items where each item’s json property contains one record from the requested resource.

For the NPS Campaigns resource, each output item represents a single NPS campaign object as returned by the Smileback API. The exact structure depends on the API response but typically includes campaign details such as ID, name, status, creation/modification timestamps, and other metadata.

If the resource is not supported, the node outputs a single item with a JSON message indicating "Resource not supported" along with the requested resource name.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential for authenticating with the Smileback API. This credential must include base URL, username, password, client ID, and client secret.
• The node uses OAuth2 password grant flow to obtain an access token before making API requests.
• The node makes HTTP GET requests to the Smileback API endpoints corresponding to the selected resource.
• Rate limiting is handled by a small delay (100ms) between paginated requests.

Troubleshooting

• Authentication errors: If the node fails to authenticate, verify that the provided API credentials (username, password, client ID, client secret) are correct and have sufficient permissions.
• Resource not supported: If you receive a message stating the resource is not supported, ensure you have selected a valid resource name. For this node, valid resources include "nps-campaigns" among others.
• Empty results: If no data is returned, check the "Last Modified Since" date filter; it may be too restrictive or incorrectly formatted.
• API rate limits or timeouts: The node includes a delay between paginated requests, but if you encounter rate limit errors, consider increasing the delay or reducing request frequency.
• Network issues: Ensure the n8n instance has network access to the Smileback API base URL.

Links and References

• Smileback API Documentation (for detailed API endpoint and data schema reference)
• OAuth 2.0 Password Grant Flow (for understanding authentication method used)