GrandCentral icon

GrandCentral

Consume GrandCentral API (Beta)

Overview

This node integrates with the GrandCentral API to perform various automation actions. Specifically, for the "Deals" resource and the "Move Deal" operation, it moves a deal to another stage within a specified deal board. This is useful in sales or CRM workflows where deals progress through different stages, such as from "Prospecting" to "Negotiation" or "Closed Won." Automating this transition helps keep deal pipelines up-to-date without manual intervention.

Practical examples:

  • Automatically move a deal to the next stage after a successful client meeting.
  • Shift deals to a "Lost" stage if no response is received after a certain period.
  • Reassign deals to different boards or stages based on changes in deal status or ownership.

Properties

Name Meaning
Authentication Method of authentication; currently supports "Access Token"
Deal The identifier of the deal to be moved
Deal Board The identifier of the target deal board where the deal will be moved
Deal Stage The identifier of the target stage within the deal board to which the deal will be moved

Output

The node outputs JSON data representing the result of the move deal action as returned by the GrandCentral API. The output is an array of objects containing details about the updated deal state after the move operation. There is no binary data output.

Dependencies

  • Requires an API key credential (access token) for authenticating requests to the GrandCentral API.
  • The node makes HTTP POST requests to the /automations/action endpoint of the GrandCentral API.
  • Proper configuration of the API credential in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or expired access token causing authentication failures.
    • Incorrect deal, deal board, or deal stage identifiers leading to errors or no effect.
    • Network connectivity problems preventing API communication.
  • Error messages and resolutions:

    • Authentication failed: Verify that the access token is valid and correctly configured.
    • Deal not found: Confirm the deal ID exists and is accessible with the provided credentials.
    • Invalid deal board or stage: Ensure the target deal board and stage IDs are correct and belong to the authenticated account.
    • API request failed: Check network connection and API service status.

Links and References

  • GrandCentral API documentation (refer to official API docs for detailed endpoint and parameter info)
  • n8n documentation on creating and using API credentials

Discussion