Instasent Data Source icon

Instasent Data Source

Send contacts and events to an Instasent Data Source

Actions3

Overview

This node, named "Instasent Data Source," allows users to send event data (and contact data) to an Instasent Data Source. Specifically for the Event - Create operation, it enables creating and sending custom events associated with a user to the Instasent platform.

Typical use cases include tracking user actions or behaviors in external systems by sending event records such as purchases, logins, or other custom-defined events. This can be useful for analytics, marketing automation, or customer engagement platforms that rely on event streams.

For example, you might use this node to send a "purchase" event with parameters like product ID and price whenever a user completes a transaction on your website.

Properties

Name Meaning
User ID Unique identifier of the user associated with the event.
Event ID Unique identifier for this event instance, used to prevent duplicate events.
Event Type Name or ID The type of event being sent. Users can select from a list of predefined event types or specify an ID via expression.
Event Date The date and time when the event occurred, formatted in ISO 8601 (e.g., YYYY-MM-DDTHH:MM:SS.SSSZ). If not provided, the current timestamp is used.
Event Parameters A collection of key-value pairs representing additional parameters for the event. The available parameter names depend on the selected event type. Users can choose from a list or specify IDs via expressions.

Output

The node outputs an array of JSON objects, each representing the response from the Instasent API for the created event. The structure of each output item corresponds to the API's response to the event creation request.

  • The main output field is json, containing the API response.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message.
  • No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Instasent API.
  • The node uses the Instasent API endpoint /stream/events to send event data.
  • The node depends on dynamic loading methods to fetch available event types and their parameters for user selection.

Troubleshooting

  • Common issues:

    • Missing or invalid User ID or Event ID may cause the API to reject the event.
    • Incorrect event type or parameters not matching the expected schema could lead to errors.
    • Network or authentication failures if the API key is missing or invalid.

  • Error messages:

    • Errors returned from the Instasent API will be surfaced in the node output under the error field if "Continue On Fail" is enabled.
    • Typical errors include validation errors for required fields or unauthorized access due to invalid credentials.

  • Resolution tips:

    • Ensure all required fields (User ID, Event ID, Event Type) are correctly set.
    • Verify the API key credential is configured properly in n8n.
    • Use the correct event parameters matching the selected event type.
    • Enable "Continue On Fail" during testing to capture error details without stopping workflow execution.

Links and References

Discussion