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 Close.com CRM to perform various operations on different CRM resources. Specifically, for the Pipeline resource with the Get Many operation, it retrieves multiple pipeline records (which represent opportunity status groups in Close.com). This is useful when you want to list or analyze all pipelines available in your CRM, for example, to display them in a dashboard, synchronize with another system, or filter opportunities by pipeline.
Practical examples:
- Fetching all pipelines to populate a dropdown menu in a workflow.
- Retrieving a limited number of pipelines for reporting purposes.
- Selecting specific fields from pipelines to reduce data volume and improve performance.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all pipeline results or only up to a specified limit. |
| Limit | The maximum number of pipeline results to return if "Return All" is false. |
| Additional Fields | Optional additional parameters; currently supports specifying a comma-separated list of fields to include in the response. |
Output
The node outputs an array of JSON objects representing pipelines retrieved from Close.com. Each object corresponds to a pipeline record and contains fields as returned by the API, potentially filtered by the "Fields" property if specified.
If binary data were involved (not applicable here), it would be summarized accordingly, but this node deals solely with JSON data representing pipeline information.
Dependencies
- Requires an API key credential for Close.com CRM to authenticate requests.
- The node depends on Close.com's REST API endpoints for pipelines.
- No additional environment variables are required beyond the API authentication setup in n8n.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API keys.
- Request limits exceeded if too many pipelines are requested without pagination.
- Incorrect field names in the "Fields" property causing empty or partial responses.
Error messages:
"The resource \"pipeline\" is not known!"— indicates an unsupported resource was selected; ensure "Pipeline" is chosen.- API errors related to permissions or rate limits will be passed through; verify API key permissions and usage quotas.
Resolutions:
- Double-check API credentials and their permissions.
- Use "Return All" carefully to avoid large data loads; prefer setting a reasonable "Limit".
- Validate field names used in "Fields" against Close.com API documentation.