Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Adobe Acrobat Details → Post Undefined

AI-generated

Overview

This node integrates with the Adobe Acrobat Details resource, specifically supporting a "Post Undefined" operation. It allows users to send a JSON body payload to an endpoint related to Adobe Acrobat Details. This can be useful for scenarios where you need to post custom or dynamic data structures to Adobe Acrobat services, such as submitting metadata, annotations, or other document-related details that are not predefined in the node.

Practical examples include:

  • Sending custom JSON data to update or create Adobe Acrobat document details.
  • Posting dynamically generated content or metadata extracted from other workflow steps.
  • Integrating Adobe Acrobat document processing with other systems by pushing JSON payloads.

Properties

Name Meaning
Body A JSON object representing the request body to be sent. The input is parsed from a JSON string and routed as the HTTP request body.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

  • json: The JSON response returned from the Adobe Acrobat API after posting the provided body.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message instead of the expected response.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Adobe Acrobat service (referred generically as an API authentication token).
  • The node expects the base URL and authentication credentials to be configured properly in the node's credentials.
  • Uses standard HTTP methods and JSON payloads to communicate with the Adobe Acrobat API.

Troubleshooting

  • Common issues:

    • Invalid or missing credentials will cause the node to throw an error indicating no credentials were returned.
    • Malformed JSON in the "Body" property will cause parsing errors before the request is sent.
    • Incorrect endpoint or unsupported operations may result in errors from the Adobe Acrobat API.

  • Error messages:

    • "No credentials returned!": Ensure that the API authentication token is correctly set up in the node credentials.
    • JSON parsing errors on the "Body" input: Verify that the JSON string is valid and properly formatted.
    • API errors returned from Adobe Acrobat: Check the response message for details; it might indicate permission issues, invalid data, or endpoint problems.

  • Enabling "Continue On Fail" allows the workflow to proceed even if some items fail, returning error details in the output.

Links and References

Discussion