Groove does not currently have an API platform.

As such, it is currently impossible for third-party services to list, view or edit any tasks. When a public API is released, this document will be updated to provide instructions on connecting Groove to Nooks so that calls tasks can be completed from the Nooks dialers and Omnidialer call history viewed within the Nooks reporting suite.

In the meantime, teams can still benefit from Nooks's parallel/power-dialing capabilities and workflows by weaving call blitzes and parallel dialing into their workflows.

Groove does not currently have an API for allowing external services to interact with its Tasks. As such, it is not possible to directly call, edit or advance Tasks through Flows directly from Nooks.
​
However, it is still possible to run workflows that harness both Groove and Nooks to build pipeline and generate revenue.

Without an external API, Nooks cannot directly intervene or interact with Groove Flows. However, it is possible to use a parallel dialer in conjunction with Flows with some creative Report construction and process automation.

The best way to modify workflows to take advantage of both Groove and Nooks functionality is to break apart your flows into pre-call and post-call segments.
​
Normally, you'd create Call Tasks within your Flow. To send these calls to Nooks, create a custom action of type Take Another Action called "Send to Nooks" and end your Flows on that action when you want them to be queued up for a calling motion.

In short, Nooks need some information to be written to SFDC about which Contacts / Leads should be called, so that they can be loaded into the Nooks Dialer. One way to pass this information is via Groove's custom SFDC fields.

Once your flows are set to end on a "Send to Nooks" step, you can pull prospects that hit these steps into Nooks by creating Reports and filtering these reports based on Groove's custom fields.
​
For example, if we wanted a report for all Groove prospects that should be called after a Flow titled "Call after 3 warm emails", we would create a Salesforce Contact Report with the following filters:
​
- Last Flow Name = "Call after 3 warm emails" (or what you named your flow

- Last Flow Step Type = "Take Another Action"
- Last Flow Status = "completed"

Any prospects that satisfy these conditions will be automatically available in the Report and thus dialable from Nooks.

There are two ways to route prospects back into Flows based on call dispositions as logged from within Nooks.
​
The simplest method is to go to the Call Library from within Nooks and filter down to prospects who should be added to another flow using a combination of filters. For example,
​
- Sequence = {SALESFORCE_REPORT_NAME}
- Disposition = "Meeting Booked"

Alternatively, you can set up two process automation Flows within SFDC that will route Prospects and Leads into particular Reports or Views so that they can be automatically added to Flows based on criteria set within Groove. If you'd like to go this route, please reach out to our enablement team to schedule a 30 minute session to ensure everything is set up correctly.

​
​