Clint Deal

Gerencia negócios (deals) da API Clint
Join our community

Actions5

Overview

This node manages deals (business transactions) using the Clint API. It supports operations to list all deals, get details of a specific deal, create a new deal, update an existing deal, and delete a deal. This node is useful for automating deal management workflows, such as syncing deals from Clint API to other systems, or managing deals programmatically within an automation.

Use Case Examples

  1. Listing all deals to display or process them in a workflow.
  2. Retrieving details of a specific deal by its ID for further analysis or updates.
  3. Creating a new deal with specified title, contact, value, group, and origin information.
  4. Updating an existing deal's details based on new information received from another system or user input.

Properties

Name Meaning
Operation Specifies the action to perform on deals: list, get, create, update, or delete.
Deal ID The unique identifier of the deal to get, update, or delete. Required for get, update, and delete operations.
Title The title or name of the deal. Used when creating or updating a deal.
Contact ID Identifier of the contact associated with the deal. Used when creating or updating a deal.
Value Monetary value of the deal. Used when creating or updating a deal.
Group ID Identifier of the group associated with the deal. Used when creating or updating a deal.
Origin ID Identifier of the origin/source of the deal. Used when creating or updating a deal.

Output

JSON

  • json - The JSON response from the Clint API for the performed operation. It contains deal data or success confirmation, or error details if the operation failed.

Dependencies

  • Clint API accessed via HTTP requests using an API token for authentication.

Troubleshooting

  • Common issues include invalid or missing API token leading to authentication errors.
  • Incorrect deal ID causing 'not found' errors when getting, updating, or deleting a deal.
  • Validation errors when creating or updating deals if required fields are missing or invalid.
  • Network or API downtime causing request failures.

Links

  • Clint API Documentation - Official documentation for the Clint API, detailing endpoints and data structures used by this node.

Discussion