Actions11
- Deals Actions
- Contact Actions
- Emails Actions
- Organization Actions
- To-Dos Actions
Overview
This node integrates with the GrandCentral API to create a new deal within a specified deal board. It is useful for automating sales pipelines by programmatically adding deals based on triggers or workflows in n8n. For example, when a new lead is captured via a form, this node can automatically create a corresponding deal in the CRM system, assigning it to an owner and linking it to an organization and optionally a contact.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "Access Token" |
| Deal Board | Identifier of the deal board where the new deal will be created (required) |
| Deal Name | Name/title of the deal to be created (required) |
| Deal Value | Monetary value associated with the deal (optional) |
| Owner | Identifier of the user who will own the deal (required) |
| No Value | Boolean flag indicating if the deal has no monetary value (optional) |
| Organization | Identifier of the organization linked to the deal (required) |
| Contact | Identifier of the contact linked to the deal (optional) |
Output
The node outputs JSON data representing the response from the GrandCentral API after creating the deal. This typically includes details about the newly created deal such as its ID, status, and other metadata returned by the API. The output is structured as an array of JSON objects, each corresponding to an input item processed.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the GrandCentral API.
- The node makes HTTP POST requests to the
/automations/actionendpoint of the GrandCentral API. - Proper configuration of the API access token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Missing required fields such as Deal Board, Deal Name, Owner, or Organization will cause the API request to fail.
- Invalid or expired API tokens will result in authentication errors.
- Incorrect identifiers for deal board, owner, organization, or contact may cause the API to reject the request or create incomplete deals.
Error messages:
- Authentication failures usually indicate invalid or missing API credentials; verify and update the API key.
- Validation errors from the API often specify which required field is missing or invalid; ensure all required properties are correctly set.
- Network or connectivity errors suggest checking internet connection or API availability.
Links and References
- GrandCentral API documentation (refer to official API docs for detailed endpoint and parameter info)
- n8n documentation on creating custom nodes and using credentials