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 the Close.com CRM platform, specifically enabling operations on various CRM resources. The "Integration Link" resource with the "Create" operation allows users to create custom integration links within Close.com. These links can be configured with a name, URL template (which supports variable placeholders), and a type indicating where the link will appear in the CRM interface (e.g., on lead, contact, or opportunity pages).
Practical scenarios include:
- Creating quick-access URLs that dynamically reference specific leads, contacts, or opportunities.
- Embedding external system links directly into Close.com records for seamless navigation.
- Automating the creation of integration links as part of workflow automation.
Example: Automatically generate an integration link named "Lead Profile" with a URL like https://example.com/lead/{{lead.id}} that appears on lead pages, allowing sales reps to quickly jump to an external profile page for each lead.
Properties
| Name | Meaning |
|---|---|
| Name | The display name for the integration link. This is how the link will be labeled in Close.com. |
| URL | The URL template for the integration link. It can include variables such as {{lead.id}} which will be replaced dynamically with actual data when displayed. |
| Type | The type of resource this integration link applies to. Options are: - Lead: Link appears on lead pages. - Contact: Link appears on contact pages. - Opportunity: Link appears on opportunity pages. |
Output
The node outputs JSON data representing the result of the integration link creation action. This typically includes details about the newly created integration link such as its ID, name, URL, and associated resource type.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Close.com API.
- The node depends on the Close.com REST API endpoint for managing integration links.
- Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Incorrect URL templates may result in malformed links or runtime errors in Close.com.
- Selecting an unsupported resource type or operation will throw an error.
Error messages:
"The resource \"integrationLink\" is not known!": Indicates the resource parameter was not recognized; ensure "Integration Link" is selected.- API errors from Close.com (e.g., 400 Bad Request) usually indicate invalid input parameters; verify the URL template and required fields.
Resolutions:
- Double-check API credentials and permissions.
- Validate URL templates for correct variable syntax.
- Confirm that all required properties are provided.