Apaleo icon

Apaleo

Interact with Apaleo API

Overview

This node interacts with the Apaleo API, specifically to check the existence of a block resource using the HTTP HEAD method. The "HEAD block exists" operation allows users to verify whether a block with a given ID exists in the Apaleo system without retrieving the full block details. This is useful for conditional workflows where subsequent actions depend on the presence or absence of a specific block.

Practical examples include:

  • Validating a block ID before attempting to update or delete it.
  • Checking if a block exists to avoid duplicate creation.
  • Conditional branching in automation based on block availability.

Properties

Name Meaning
Block ID ID of the block to check for existence

The node requires the user to provide the "Block ID" which uniquely identifies the block resource in Apaleo.

Output

The output JSON will contain information indicating whether the block exists. Since this is a HEAD request, the response typically does not include a body but the node will reflect success or failure accordingly.

  • If the block exists, the node outputs an empty JSON object or metadata confirming existence.
  • If the block does not exist, an error or empty result may be returned depending on the API response and node configuration.

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the Apaleo API.
  • Needs an API authentication token (access token) configured in the node credentials.
  • The base URL used is https://api.apaleo.com.

Troubleshooting

  • Common issues:

    • Invalid or missing Block ID will cause the operation to fail.
    • Expired or invalid API access token will result in authentication errors.
    • Network connectivity issues can prevent reaching the Apaleo API endpoint.
  • Error messages:

    • "Block not found" or similar indicates the block ID does not exist.
    • Authentication errors suggest checking the API credentials.
    • Timeout or network errors require verifying internet connection and API availability.

To resolve these, ensure the Block ID is correct, refresh or reconfigure API credentials, and confirm network access.

Links and References

Discussion