Actions79
- Lead Actions
- Lead Status Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Pipeline Actions
- Email Template Actions
- Task Actions
- User Actions
- Template Actions
- Custom Field Actions
Pipeline → Get
AI-generatedOverview
This node integrates with the Close.com CRM platform, specifically allowing operations on various CRM resources. For the Pipeline - Get operation, it retrieves detailed information about a specific pipeline (which represents opportunity status groups in Close.com). This is useful when you want to fetch the current configuration or details of a pipeline by its ID.
Practical scenarios include:
- Fetching pipeline details to display or process in workflows.
- Using pipeline data to drive conditional logic or reporting.
- Synchronizing pipeline information with other systems.
Properties
| Name | Meaning |
|---|---|
| Pipeline ID | The unique identifier of the pipeline to retrieve. This is required. |
| Additional Fields | Optional extra fields to include in the response. You can specify a comma-separated list of field names to customize the returned data. |
Output
The node outputs JSON data representing the pipeline object retrieved from Close.com. The structure includes all standard pipeline properties and any additional fields requested via the "Fields" input property.
The output JSON typically contains:
- Pipeline metadata such as ID, name, description.
- Status groups within the pipeline.
- Any custom or additional fields specified.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- The node uses Close.com's REST API endpoints to perform actions.
- No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Pipeline ID will cause errors.
- Insufficient permissions or invalid API credentials may result in authentication failures.
- Specifying invalid field names in "Additional Fields" may lead to incomplete or error responses.
Error messages:
"The resource "pipeline" is not known!"— indicates an unsupported resource was selected; ensure "Pipeline" is chosen.- API errors from Close.com (e.g., 404 Not Found) usually mean the pipeline ID does not exist or is inaccessible.
Resolutions:
- Verify the Pipeline ID is correct and exists in your Close.com account.
- Check that the API key has sufficient permissions.
- Use valid field names for additional fields or leave empty to get default data.