CloudConvert Trigger icon

CloudConvert Trigger

Process CloudConvert Job Webhooks

Overview

This node acts as a trigger for CloudConvert job webhooks, allowing workflows to respond to specific CloudConvert job events such as job creation, completion, or failure. It is useful for automating processes based on the status of file conversion jobs handled by CloudConvert, for example, triggering further processing when a job finishes or handling errors when a job fails.

Use Case Examples

  1. Automatically start a workflow when a CloudConvert job finishes to process the converted files.
  2. Receive notifications and trigger error handling workflows when a CloudConvert job fails.

Properties

Name Meaning
Events To Subscribe To Specifies which CloudConvert job events the node should listen for notifications about, such as job creation, job finished, or job failed.
Download? Determines whether to download result files from synchronous requests and add them as binary attachments to the workflow data.
Verify Signature? Indicates whether to validate the webhook signature to ensure the webhook request is authentic.

Output

Binary

Contains downloaded result files from CloudConvert export tasks if the 'Download?' option is enabled and the job event is 'job.finished'. The binary property names correspond to the export task names defined in the job.

JSON

  • json - The JSON payload of the webhook event received from CloudConvert, containing details about the job and event.
  • binary - Binary attachments of downloaded export files if the download option is enabled and applicable.

Dependencies

  • Requires an API key credential with 'webhook.read' and 'webhook.write' scopes for CloudConvert API access.

Troubleshooting

  • If webhook signature verification is enabled but the signature does not match, the node will ignore the webhook request. Ensure the webhook signing secret is correctly stored and the CloudConvert webhook is properly configured.
  • If the node is running on localhost, webhook registration is bypassed, which may cause webhook events not to be received externally.
  • Ensure the API key used has the necessary scopes ('webhook.read' and 'webhook.write') to manage webhooks and receive events.

Links

Discussion