n8n Integration – Credentials
2 minutes to readTo connect Caspio with n8n, create a Caspio API profile. This allows n8n to authenticate securely and perform actions in your account.
Connecting n8n to Caspio
- In your Caspio account, create an API profile, or choose an existing one. See API profiles.
- On the profile’s Permissions tab, grant access to the tables and views the n8n integration should reach.
- On the Credentials tab, copy the Client ID, Client secret, and Integration URL. You will need the Client ID, Client Secret, and Integration URL for connecting n8n to Caspio.
- In your n8n account, install the Caspio node:
- In the left panel, click the plus icon and select Workflow.
- In the new workflow, click Add first step and in the right panel, look up Caspio.
- Next to Caspio, click Install node.
- In the left panel, click the plus icon and select Credential.
- In the Add new credential window, select Caspio OAuth2 API and click Continue.
- Paste the Client ID, Client Secret, and Integration URL from your API profile in Caspio. Click Save to test the credential.
After a successful setup, the Caspio credential can be reused in multiple workflows.
Ending integration with n8n
If you decide to stop using n8n with Caspio, it is important to follow the correct order of steps to avoid leaving inactive webhooks or credential errors:
- Delete your workflows in n8n first. This ensures that n8n no longer attempts to connect to Caspio using the credentials you provided.
- After deleting workflows, remove the associated API profile in Caspio.
Following this order prevents orphaned webhook connections and ensures your Caspio environment remains clean after ending integration with n8n.
Note: If you already removed the API profile before deleting the workflows, log in to your Caspio account and, in Outgoing Webhooks, manually delete relevant webhooks that use the n8n outgoing URLs.
If you accidentally deleted an outgoing webhook that is required by an active n8n workflow, you can deactivate that workflow in n8n and then activate it again. This ensures that all the required webhooks are recreated.