Output.Rocks Trigger icon

Output.Rocks Trigger

Starts the workflow when a webhook is called

Overview

The Output.Rocks Trigger node is a webhook trigger for n8n workflows. It listens for incoming HTTP POST requests at a user-defined path and starts the workflow when such a request is received. The node requires basic authentication using credentials defined in the node settings. This node is particularly useful for integrating external systems or services that can send data to your n8n workflow via webhooks, especially when you need to securely receive files or payloads.

Practical examples:

  • Receiving documents or files from an external service and processing them automatically.
  • Integrating with third-party platforms that support sending data via webhooks (e.g., Output.Rocks).
  • Automating workflows based on events triggered by external applications.

Properties

Name Type Meaning
Path String The path to listen to for webhook calls. This defines the endpoint URL segment where the node will accept incoming POST requests.

Output

  • json.body: Contains the parsed body of the incoming POST request.
  • binary["Rendered document"]: If the incoming request includes a base64_file field in its body, this field will be decoded from base64 and attached as binary data under the name "Rendered document".

Example output structure

{
  "json": {
    "body": {
      // All fields sent in the POST request body
    }
  },
  "binary": {
    "Rendered document": {
      // Binary file metadata and data, if provided
    }
  }
}

Dependencies

  • External Service: Requires valid credentials (clientIdentifier and webhookSecretKey) for basic authentication, configured in the node's credentials (outputRocksTriggerApi).
  • n8n Configuration: No special environment variables are required, but the workflow must be active to use the production webhook URL.

Troubleshooting

  • Missing Authentication Data:
    Error: "No authentication data defined on node!"
    Solution: Ensure that the node has valid credentials set up in the n8n credential manager.

  • Unauthorized Access:
    Error: "Authorization is required!"
    Solution: The request did not include any authentication. Make sure to provide basic auth headers.

  • Forbidden Access:
    Error: "Authorization data is wrong!"
    Solution: The provided username or password does not match the credentials configured in the node.

  • Binary Data Issues:
    If the base64_file field is missing or malformed, the binary output may be empty or cause errors in downstream nodes.

Links and References

Discussion