MagicDoor icon

MagicDoor

Interact with MagicDoor API
Join our community

Actions13

Overview

The node "MagicDoor" is designed to interact with the MagicDoor API, providing various operations grouped under different resources. Specifically, for the Sales resource and the Get Demo Request operation, it retrieves details of a particular demo request by its ID. This node is useful in scenarios where you want to programmatically fetch information about demo requests from MagicDoor, such as integrating demo request data into workflows for follow-up, reporting, or automation.

Example use cases:

  • Automatically retrieving demo request details when a new request is created.
  • Integrating demo request data into CRM or marketing tools.
  • Generating reports or notifications based on demo request information.

Properties

Name Meaning
Demo Request ID The ID of the demo request to retrieve.

This property is required and expects a number representing the unique identifier of the demo request.

Output

The node outputs JSON data containing the details of the requested demo request fetched from the MagicDoor API. The exact structure depends on the API response but typically includes fields describing the demo request's attributes (e.g., requester info, status, timestamps).

If the node supports binary data output, it would represent any files or attachments related to the demo request; however, this is not indicated in the provided code snippet.

Dependencies

  • Requires an API key credential for authenticating with the MagicDoor API.
  • The base URL for the API is configured via credentials.
  • The node uses HTTP requests to communicate with the MagicDoor API endpoints.

Troubleshooting

  • Missing or invalid Demo Request ID: Ensure that the Demo Request ID is provided and is a valid number.
  • Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • API connectivity issues: Check network connectivity and the correctness of the base URL.
  • HTTP errors: Since the node ignores HTTP status errors by default, check the returned JSON for error messages if the output is empty or unexpected.

Links and References

Discussion