97Display Assign User icon

97Display Assign User

Assign User notifications via 97Display notification API

Overview

This node integrates with the 97Display notification API to assign a user to a lead within an organization’s workflow. It is designed to automate the process of assigning leads to specific users based on selections made in the node's configuration or dynamically loaded user lists.

Common scenarios where this node is beneficial include:

  • Automatically assigning incoming leads to sales representatives.
  • Distributing workload among team members by assigning users programmatically.
  • Integrating lead assignment into larger automated workflows for CRM or marketing systems.

For example, when a new lead is captured via a webhook, this node can assign that lead to a selected user by sending the assignment information to the 97Display API.

Properties

Name Meaning
Organization ID The identifier of the organization; automatically populated from incoming webhook data.
Workflow ID The identifier of the current workflow; automatically set to the running workflow's ID.
AssignUser Select a user to assign the lead to. The list of users is dynamically loaded from the API.
APIKey The API key used to authenticate requests to the 97Display API; sourced from environment variables.

Output

The node outputs JSON data representing the response from the 97Display API after attempting to assign the user to the lead. Each output item corresponds to one input item processed and contains either:

  • The successful API response JSON confirming the assignment.
  • An error object with an error property describing the failure if the request failed and the node is configured to continue on failure.

No binary data is produced by this node.

Dependencies

  • Requires access to the 97Display notification API at https://itapi.api97.com and https://notificationapi.api97.com.
  • Needs an API key credential provided via an environment variable (MY_API_KEY) for authenticating API requests.
  • Relies on webhook input data containing OrganizationId and LeadId fields.
  • Uses dynamic loading of users from the API endpoints /Lead/GetUsers or /Lead/GetUsersByWorkflow.

Troubleshooting

  • Failed to load users: If the node cannot retrieve users for the "AssignUser" dropdown, it falls back to a default option indicating failure. This may be due to invalid API keys, network issues, or incorrect organization/workflow IDs.
  • API request errors: Errors during the POST request to assign a user will throw exceptions unless "Continue On Fail" is enabled, in which case the error message is returned in the output JSON.
  • Invalid user selection: The node expects the user selection to be a JSON string containing an id field or a plain string user ID. Malformed inputs may cause parsing errors.
  • Missing webhook data: The node depends on webhook data for OrganizationId and LeadId. Missing or malformed webhook payloads will cause failures.

To resolve these issues:

  • Verify the API key is correctly set in environment variables.
  • Ensure webhook payloads contain required fields.
  • Check network connectivity to the API endpoints.
  • Confirm the organization and workflow IDs are valid and correspond to existing entities in the 97Display system.

Links and References

Discussion