Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
This node integrates with a CRM system to perform various operations on different resources such as leads, contacts, opportunities, and integration links. Specifically, the "Integration Link" resource with the "Update" operation allows users to update existing integration links by modifying their name, URL template, or associated resource type.
Common scenarios for this node include automating updates to integration links when URLs or naming conventions change, or when the type of resource the link applies to needs adjustment. For example, if an integration link pointing to lead data changes its URL format, this node can update that link automatically within a workflow.
Properties
| Name | Meaning |
|---|---|
| Link ID | The unique identifier of the integration link to update. |
| Update Fields | A collection of fields to update on the integration link: |
| Name | The new display name for the integration link. |
| URL | The new URL template for the integration link, supporting placeholders like {{lead.id}}. |
| Type | The new type of resource this integration link applies to. Options: Lead, Contact, Opportunity. |
Output
The node outputs JSON data representing the updated integration link object returned from the CRM API after the update operation. This typically includes the updated fields such as the link's ID, name, URL, type, and any other metadata provided by the service.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the CRM service.
- The node depends on the CRM's REST API endpoints for integration link management.
- Proper network access to the CRM API is necessary.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Link ID will cause the update to fail.
- Providing invalid URL templates or unsupported placeholders may result in API errors.
- Attempting to update a non-existent integration link will return an error.
- Insufficient permissions or expired API credentials can cause authentication failures.
Error messages and resolutions:
"The resource "integrationLink" is not known!"— Ensure the resource parameter is correctly set to "integrationLink".- API errors related to invalid input usually indicate malformed fields; verify the URL format and field values.
- Authentication errors require checking the API key credential validity and permissions.
- Network errors suggest connectivity issues to the CRM API endpoint.
Links and References
- Refer to your CRM provider’s API documentation for integration link management and URL templating syntax.
- n8n documentation on creating and using API credentials for authenticated nodes.