97Display Update Status icon

97Display Update Status

Update Status notifications via 97Display notification API

Overview

This node integrates with the 97Display notification API to update the status of a lead within a workflow. It is designed to be used in automation workflows where lead statuses need to be programmatically updated based on external triggers or internal logic. Typical use cases include updating lead progress in CRM systems, notifying other services about status changes, or tracking workflow execution states.

For example, when a webhook receives new lead data, this node can update that lead's status by sending the relevant information to the 97Display API, ensuring that the lead's current state is accurately reflected in connected systems.

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 active workflow's ID.
Status The new status to assign to the lead. Options are dynamically loaded from the 97Display API.
APIKey The API key used for authenticating requests to the 97Display API; sourced from environment.

Output

The node outputs an array of JSON objects, each representing the response from the 97Display API after attempting to update a lead's status. Each output item contains the full JSON response returned by the API call.

If the node encounters an error during execution and is configured to continue on failure, it outputs an object with an error field containing the error message.

No binary data is produced by this node.

Dependencies

  • Requires access to the 97Display notification API at https://itapi.api97.com.
  • Needs an API key credential for authentication, which must be provided via an environment variable.
  • The node dynamically loads available status options from the API endpoint /Lead/GetStudentRoles.
  • The node expects to receive lead data (including LeadId and OrganizationId) from a preceding webhook or similar trigger.

Troubleshooting

  • Error loading statuses: If the node cannot load status options, it will show a default option indicating an error. This usually means the API key is invalid or the API service is unreachable.
  • API request failures: Errors during the status update POST request may occur due to invalid API keys, incorrect lead IDs, or network issues. Ensure the API key is valid and the lead data is correctly passed.
  • JSON parsing errors: The status parameter is expected to be a JSON string containing an id field or a plain string. Malformed JSON in the status property can cause parsing errors.
  • Missing lead data: If the LeadId or OrganizationId is not present in the webhook payload, the API call will fail. Verify that the incoming webhook includes these fields.

Links and References

Discussion