web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

Atribuir Tarefa - Power Automate - CRM

(1) ShareShare
ReportReport
Posted on by 6

lá, pessoal!

 

Criei um fluxo no Power Automate com a seguinte condição:

 

Ao criar um Lead no CRM, caso o campo Tipo esteja preenchido como PROSPECTADO, as atividades devem ser atribuídas de forma automática.

 

O fluxo é processado com êxito, porém a tarefa não é criada e tampouco fica vinculada à tabela Lead.

 

Alguém já passou por esse problema ou saberia o que pode estar faltando na configuração?

 

Agradeço desde já pela ajuda!

 

~

Hey everyone!
I created a flow in Power Automate with the following condition:
When creating a Lead in the CRM, if the Type field is filled with PROSPECTED, the activities should be assigned automatically.
The flow is processed successfully, but the task is not created nor is it linked to the Lead table.
Has anyone else experienced this problem or know what might be missing in the configuration?
Thanks in advance for your help!

Categories:
I have the same question (0)
  • Verified answer
    Tom_Gioielli Profile Picture
    2,497 Super User 2025 Season 2 on at
    Atribuir Tarefa - Power Automate - CRM
    I created a quick sample flow that you can see below. The "Type" field you are mentioning seems like a custom one, so I can't show you exactly how this should look but the below should get you going. If you want to post some more specifics I can probably help more.
     
    • Trigger on the creation of a lead record by using the "When a New Row Is Added" trigger for Dataverse.
    • I prefer to add a filter directly to the trigger, so that only leads that meet the criteria trigger the flow. (The alternative is to trigger it for every created lead, then add a condition later in the flow.)
      • The trigger should be formatted as follows:  {type field schema} eq {Prospected option set value}. Assuming you have a field called "new_type" and the PROSPECTED option has a value of 515000231 it would look like this.
     
    • After that, you can do the "Add a New Row" action in Dataverse to create the task. Add in your Topic, Description, and Due Date. Then make sure you populate the Regarding (Leads) field like so (note that I cropped this image for space. The Leads entry is a little way down the inputs).
     
    ----------------------------------------------------------------
    So, the entire flow only needs to be two steps. One to trigger when a Lead of type Prospect is created, and the other to create the task and associate it to the lead. Let me know if you have specific field names or other problems with this!
  • LA-03111723-0 Profile Picture
    6 on at
    Atribuir Tarefa - Power Automate - CRM
    Muitoo Obrigada!!
     
    Deu super certo, seguindo essas instruções que passou.
     
    Ao invés de estar utilizando o filtro pelo tipo de campo, eu estava tentando incluir como CONDIÇÃO e me dava erro, dessa forma que indicou, processou super rápido!
     
    Agora estou estudando para que no momento da criação do lead, com esse filtro especifico ele inclua essa atividade na linha do tempo com a referencia do lead criado.
     
    Tarefa vem assim:
     
     e preciso que venha assim:
     
     
    Teria alguma sugestao?
     
    Obrigada. 
  • Suggested answer
    Tom_Gioielli Profile Picture
    2,497 Super User 2025 Season 2 on at
    Atribuir Tarefa - Power Automate - CRM
    Glad to hear it is working so far. On the step to Create the new Task, did you make sure to populate the Regarding (Leads) like my screenshot above? If you did, then the Regarding Field on your task should be populated to the lead as expected. The regarding field would be set as follows.
     
    leads({leadid})
     
    You can grab the Lead ID, which is the unique identifier for the record, from your dynamic content off the trigger.
     
    In terms of this being created immediately, Power Automate flows always run in the background. This means there is always going to be a delay of 1-5 seconds before the task is created and associated to the lead. If you need it to be immediate, then you probably want to use a Real-Time CRM workflow to create the task.
     
    That would be a relatively easy setup and task creation, and it has the benefit that it can run during the creation process of the lead. This would ensure it shows up on the timeline as soon as the lead is created without any delay.
     
    -----------------------------------------------------------------------------------------------

    Que bom saber que está funcionando até agora.

    Na etapa de Criar a nova Tarefa, você verificou se preencheu o campo Referente (Leads) como na minha captura de tela acima? Se fez isso, então o campo Referente na sua tarefa deve estar preenchido com o lead conforme esperado. O campo referente seria definido da seguinte forma:

     

    leads({leadid})


    Você pode obter o ID do Lead, que é o identificador único do registro, a partir do conteúdo dinâmico do gatilho.

     

    Quanto à criação imediata, os fluxos do Power Automate sempre são executados em segundo plano. Isso significa que sempre haverá um atraso de 1 a 5 segundos antes que a tarefa seja criada e associada ao lead. Se você precisa que seja imediato, então provavelmente vai querer usar um workflow em tempo real do CRM para criar a tarefa.

    Essa seria uma configuração relativamente fácil e a criação da tarefa teria a vantagem de ser executada durante o processo de criação do lead. Isso garantiria que apareça na linha do tempo assim que o lead for criado, sem nenhum atraso.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 162 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 103

#3
MVP-Daniyal Khaleel Profile Picture

MVP-Daniyal Khaleel 87

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans