97Display Assign User icon

97Display Assign User

Assign User notifications via 97Display notification API

97Display Assign User

AI-generated

Overview

This node sends user assignment notifications via the 97Display notification API. It is designed to send emails either using predefined email templates or custom subject and body content. The node is useful in workflows where automated notifications need to be sent to users based on dynamic data received from a webhook, such as notifying users about task assignments, updates, or alerts within an organization.

Practical examples include:

  • Sending assignment notifications to users when a new task is created.
  • Informing users with templated emails that include personalized tokens like location or organization name.
  • Using custom email content when no template fits the use case.

Properties

Name Meaning
Organization ID Hidden property automatically set from incoming webhook data; identifies the organization context.
Workflow ID Hidden property set to the current workflow's ID.
Use Email Template? Boolean flag to choose between sending an email using a predefined template (true) or custom content (false).
Email Template Dropdown list of available email templates loaded dynamically from the API; required if "Use Email Template?" is true.
Subject Custom email subject line; required if not using an email template.
Body Custom email body content; required if not using an email template.
Is HTML Email Hidden boolean indicating whether the email should be sent as HTML (default is false, i.e., plain text).
APIKey Hidden property for the API key used to authenticate requests to the notification API; sourced from environment variable.

Output

The node outputs an array of JSON objects, each representing the response from the notification API for each input item processed. Each output JSON contains the API's response to the assign user notification request, which typically includes status information about the notification sent.

No binary data is output by this node.

Dependencies

  • Requires access to the 97Display notification API at https://notificationapi.api97.com.
  • Needs an API key credential configured as an environment variable (MY_API_KEY) for authenticating API requests.
  • Relies on webhook input data containing user and organization details, including email addresses and tokens for personalization.
  • Uses dynamic loading of email templates from the API endpoint /api/Email/GetByWorkflow.

Troubleshooting

  • Error loading templates: If the node fails to load email templates, it will show an error option in the dropdown. This usually indicates network issues or invalid API key. Verify API key validity and network connectivity.
  • Invalid template JSON: When selecting a template, if the stored template string cannot be parsed as JSON, the node falls back to using the raw string as the template ID. Ensure templates are correctly formatted.
  • Missing required fields: If required properties like Subject or Body (when not using a template) are empty, the node will likely throw validation errors. Always provide these fields accordingly.
  • API request failures: Errors returned from the notification API (e.g., authentication failure, invalid parameters) will cause the node to throw unless "Continue On Fail" is enabled, in which case error details are included in the output JSON.
  • Incorrect token usage: Tokens like @LocationEmail and @OrganizationName must be present in the webhook payload under Tokens. Missing tokens may result in incomplete or incorrect email content.

Links and References

Discussion