# salesforce task creation + tokens

**URL:** <https://community.hubspot.com/t/salesforce-task-creation-tokens/26059>\
**Category:** Lists, Lead Scoring & Workflows\
**Tags:** workflows\
**Created:** [September 28, 2020, 2:22pm UTC](https://community.hubspot.com/t/salesforce-task-creation-tokens/26059 "2020-09-28T14:22:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Melly2022](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/melly2022/32/81147_2.png) [@Melly2022](https://community.hubspot.com/u/Melly2022)\
**Post date:** [September 28, 2020, 2:22pm UTC](https://community.hubspot.com/t/salesforce-task-creation-tokens/26059/1 "2020-09-28T14:22:46Z")

</div>

Is there a way to pull tokens into salesforce task creations in workflows

---

<div class="post-metadata">

**Author:** ![Phil\_Vallender](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/phil_vallender/32/48924_2.png) [@Phil\_Vallender](https://community.hubspot.com/u/Phil_Vallender)\
**Post date:** [September 28, 2020, 6:15pm UTC](https://community.hubspot.com/t/salesforce-task-creation-tokens/26059/2 "2020-09-28T18:15:36Z")

</div>

Hi @Melly2022

It doesn’t look like it currently - no personalise/token in the create Salesforce task action settings.

If you want to create more complex tasks, you might want to use Process Builder on the Salesfroce side instead.

Hope this help.

---

<div class="post-metadata">

**Author:** ![Melly2022](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/melly2022/32/81147_2.png) [@Melly2022](https://community.hubspot.com/u/Melly2022)\
**Post date:** [October 2, 2020, 7:36pm UTC](https://community.hubspot.com/t/salesforce-task-creation-tokens/26059/3 "2020-10-02T19:36:01Z")

</div>

Hi Phil

sadly this doesnt help much. We use Hubspot for marketing and salesforce for sales - marketing assigns the tasks to the Sales team from Hubspot in workflows… It would be so great if we could pull in tolkens from the contact record

process builders in SF are clumsy and will just triple up on work in this case - a task is in the activity history because a form was submitted then a task was assigned then a task was created to notify them to go look at the task that was created and the form that was submitted.

I hope that makes sense.