So far we've focused mostly on showing you how to track and monitor specific elements of your project management. Being able to quickly track and report technical issues, and create tickets is handy, but it doesn't encompass the entire spectrum of running your business. Before we get into managing a project, sales and BizDev teams work to provide leads, that they turn into opportunities, and finally to win deals. Being able to track a deal through every cycle of the sales process could potential win or lose a deal.
That's why we thought of an easy way to create and update deals in Pipedrive, and spreading that information to Jira and Confluence, and finally as an email summary.
Time to construct our workflow. By now you should have an account, but if not, go ahead and register. It's free!
From there we dive right into the interesting part - creating your workflow.
We'll begin by creating a deal in Pipedrive. Deal Created would be the trigger that will start our schema every time you have a new deal.
Here we set the deal stage and status. If needed, you can put additional values such as deal value, responsible person, organization and dates of creation.
Simultaneously Cloudpipes will create an issue in Jira.
We mapped the summary and description with information from the Pipedrive deal, which we also linked to the Jira issue. Linked objects can always be fetched later. Once linked, you can access specific objects through other pipelines, thus achieving bi-directional transfer of information.
Right after that Cloudpipes will create a sub-page in Conflunece.
HHere we filled out the body field with information from the Pipedrive deal. Furthermore, we can add a label to our sub-page if needed. Just choose the Create a Label pipe from the list of Confluence pipes, associate it with an already existing Confluence page or pipe, and give it a name.
Once we submit all the information needed in Confluence, Cloudpipes will circle back to update the Pipedrive deal with the newly created Confluence page's URL.
If you previously forgotten, you can apply addition values when updating the deal.
Lastly, we'll use our built-in email channel to send a summary of the deal.
Here, we basically put the Pipedrive deal's URL, the Jira ticket and Confluence page. We can also drag and drop any other information regarding any of our pipes that you might need.
That's been another case of workflow automation using Cloudpipes. Create and update deals in real time, and share the information with your team with an easy to replicate workflow schema.
Not sure how Cloudpipes works? Become a pro with your free complimentary tutorial now!