CiviCRM is a community node (@ixiam/n8n-nodes-civicrm), not a built-in n8n node. That’s why it was installable on your self-hosted instance but isn’t available on Cloud.
Workaround:
Use the HTTP Request node as a workaround. CiviCRM has a REST API (v4). You can call it directly with the HTTP Request node using Header Auth with your CiviCRM API key. It’s more manual but works on any n8n instance.
@BackOfficeSupport CiviCRM is a community node (n8n-nodes-civicrm on npm), not a built-in — n8n Cloud doesnt allow user-installed community nodes at all, only the curated set the n8n team has whitelisted, which CiviCRM isnt on. on self-hosted u can install any npm community node via Settings → Community Nodes, which is why it worked there. workarounds for Cloud are either the HTTP Request node + CiviCRM REST API directly, or asking n8n support to add CiviCRM to the whitelist. how heavily does the workflow rely on the node — a couple operations or deep usage?
Hi
Thanks for the info. We’ve built several integrations for CiviCRM with the HTTP node approach.
I’m a bit confused. I was under the impression that any integrations listed here Best apps & software integrations | n8n were fully vetted and approved. There are only integration listed there that are available in n8n cloud.
Just to clarify the situation a bit: the CiviCRM node we maintain from Ixiam is indeed available in n8n Cloud. In fact, it has been validated and verified by n8n as a Verified Community Node, so it can be installed on both self-hosted instances and Cloud.
Perhaps the confusion comes from the fact that there is an older version of the node, n8n-nodes-civicrm, which we no longer maintain and was discontinued some time ago. We currently recommend using @ixiam/n8n-nodes-civicrm, which is the official verified version and the one that continues to receive updates and support.
