ACP icon

ACP

Consume ACP API
Join our community

Overview

This n8n node, named ACP, is designed to integrate with the ACP API. Its primary function is to pause (wait) the workflow execution until it is resumed by an external webhook call. This is useful in scenarios where you need to wait for an asynchronous event or callback from an external system before continuing your automation.

Common use cases:

  • Waiting for a user action or approval via an external app before proceeding.
  • Pausing workflow execution until a third-party service sends a callback (e.g., payment confirmation, data processing completion).
  • Implementing long-polling or manual triggers within automated processes.

Practical example:
A workflow that creates a record in an external system and then waits for a status update via a webhook before moving forward.

Properties

Name Type Meaning
Select App or Module resourceLocator The ID of the app or module to associate with this webhook. Can be selected from a list or entered as ID.
Webhook HTTP Method options The HTTP method (GET, POST, etc.) that the webhook will listen for.
Options → Ignore Bots boolean If enabled, requests from bots (like link previewers or crawlers) are ignored.

Note: "Notice" properties are informational only and do not affect node behavior.

Output

The node does not produce any output data immediately when executed. Instead, it puts the workflow into a waiting state. When the specified webhook is called, the workflow resumes and outputs a single item containing:

{
  "headers": { /* HTTP headers from the webhook request */ },
  "params": { /* URL parameters from the webhook request */ },
  "query": { /* Query string parameters from the webhook request */ },
  "body": { /* Body of the webhook request, if present */ }
}
  • Binary Data: The node can output binary data, but in this implementation, the binary field is always empty ({}).

Dependencies

  • External Service: Requires access to the ACP API.
  • Credentials: Needs valid acpApi credentials configured in n8n.
  • Environment: The webhook URL must be accessible from the external system that will trigger it.

Troubleshooting

Common Issues:

  • Webhook Not Triggered: Ensure the external system calls the correct webhook URL with the right HTTP method.
  • Authorization Errors: If "Ignore Bots" is enabled, bot-originated requests will be rejected. Make sure legitimate requests have proper user-agent headers.
  • Workflow Does Not Resume: Double-check the appId and ensure the webhook path matches the configuration.

Error Messages:

  • "Authorization data is wrong!": This occurs if a bot is detected (when "Ignore Bots" is enabled). To resolve, disable "Ignore Bots" or ensure the request is not coming from a bot/crawler.

Links and References

Discussion