1.8 KiB
| contentType |
|---|
| explanation |
Custom API operations
n8n supplies hundreds of nodes, allowing you to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around this by making a custom API call using the HTTP Request node.
One of the most complex parts of setting up API calls is managing authentication. n8n simplifies authentication for services with an existing node.
n8n includes credential-only nodes. These are integrations where n8n supports setting up credentials for use in the HTTP Request node, but doesn't provide a standalone node.
Predefined credential types
A predefined credential type is a credential that already exists in n8n. You can use predefined credential types instead of generic credentials in the HTTP Request node.
For example: you create an Asana credential, for use with the Asana node. Later, you want to perform an operation that isn't supported by the Asana node, using Asana's API. You can use your existing Asana credential in the HTTP Request node to perform the operation, without additional authentication setup.
Using predefined credential types
--8<-- "_snippets/integrations/predefined-credential-type-how-to.md"
Credential scopes
Some existing credential types have specific scopes: endpoints that they work with. n8n warns you about this when you select the credential type.
For example, follow the steps in Using predefined credential types, and select Google Calendar OAuth2 API as your Credential Type. n8n displays a box listing the two endpoints you can use this credential type with:
