HTTP Request Tool in AI Agent Fails to Recognize Generic OAuth2 Credential for Pardot API

Explanation

The error “Credentials not found” generally means that the HTTP Request Tool in your AI agent isn’t picking up your generic OAuth2 credentials. Although both the classic HTTP Request node and the HTTP Request Tool use HTTP Request credentials, differences in how AI agents resolve credential references may lead to this inconsistency.

What to Check

• Credential Attachment:
  Verify that the generic OAuth2 credential you set up is correctly attached in the HTTP Request Tool configuration. Ensure that the credential name/reference exactly matches what the node expects.

• Global vs. Node-Scoped Credentials:
  Confirm that the credential is saved globally so that all nodes—including those invoked by AI agents—can access it. Sometimes, a credential saved in one context (e.g. as a node-specific credential) might not be visible in another.

• Tool Limitations:
  The AI agent’s HTTP Request Tool might be optimized for predefined credential types. In environments where a custom or generic OAuth2 credential type is used (especially for APIs with non-standard scopes like Pardot/Salesforce Account Engagement), it’s possible this setup isn’t fully supported.

Suggested Workarounds

• Try re-attaching the credential in the AI tool’s settings (or re-creating it as a global credential) to see if that resolves the mismatch.
• If possible, check for any available updates or patches for the AI agent since improvements or bug fixes in credential detection might be part of newer releases.
• Alternatively, if the classic HTTP Request node works as expected, consider using that within your workflow as a temporary solution.

If these steps don’t resolve the issue, it might be necessary to report the behavior on the n8n issue tracker so that improvements can be made around generic OAuth2 credential support in the HTTP Request Tool for AI agents.