# Workflow with multiple data sources

**URL:** <https://community.hubspot.com/t/workflow-with-multiple-data-sources/71231>\
**Category:** HubSpot Ideas\
**Tags:** workflows\
**Created:** [December 14, 2022, 6:40pm UTC](https://community.hubspot.com/t/workflow-with-multiple-data-sources/71231 "2022-12-14T18:40:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SealaB](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sealab/32/88952_2.png) [@SealaB](https://community.hubspot.com/u/SealaB)\
**Post date:** [December 14, 2022, 6:40pm UTC](https://community.hubspot.com/t/workflow-with-multiple-data-sources/71231/1 "2022-12-14T18:40:08Z")

</div>

I am raising this idea post on behalf of a customer who was working within workflows and needs better functionality of crossing data sources.

We were specifically working to remove a contact from a sequence based on their Pipeline stage - and found this automation particularly difficult as it is not possible to pull associated contacts into a sequence from a deal-based workflow.

Ideally, it would be wonderful to have multiple data-sets available within a workflow in order to best access the contacts who have an associated deal in the correct deal stage.

We reviewed utilizing if/then branches within a contact-based workflow, but there is a certain counter-intuitiveness to not being able to access this info from the deal side, and only being able to pull from the contact end.

Being able to create a workflow that accesses multiple data points would rectify this issue among many others, but I felt this was specifically a great exmaple of this feature request, and am posting here accordingly.

---

<div class="post-metadata">

**Author:** ![kennedyp](https://avatars.discourse-cdn.com/v4/letter/k/49beb7/32.png) [@kennedyp](https://community.hubspot.com/u/kennedyp)\
**Post date:** [December 14, 2022, 7:00pm UTC](https://community.hubspot.com/t/workflow-with-multiple-data-sources/71231/2 "2022-12-14T19:00:46Z")

</div>

This would be awesome-- especially if we could then copy/set property values across objects too

---

<div class="post-metadata">

**Author:** ![FlyingAnds](https://avatars.discourse-cdn.com/v4/letter/f/ee7513/32.png) [@FlyingAnds](https://community.hubspot.com/u/FlyingAnds)\
**Post date:** [December 19, 2022, 10:41am UTC](https://community.hubspot.com/t/workflow-with-multiple-data-sources/71231/3 "2022-12-19T10:41:34Z")

</div>

Yes please!  
I’m having this issue now with a workflow that’s ticket/contact-based.  
The current workaround is a another workflow that gets the contact property and copies it to a ticket property. It’s the exact same information, but I need it in a ticket based workflow.