Flow / Power Automate - Add Conditional “IF” Actions in Power Automate Video

Discover how to add conditional 'if' actions in Power Automate to automate the acceptance of meeting invitations with specific keywords. Learn to create automated flows, manage conditions, and set up actions based on conditions. See how to respond to invitations, simulate invitations, and ensure proper handling of configured conditions. Watch now to streamline your workflow and enhance efficiency!

  • 03:06
  • 184 views

Objectifs :

This video aims to teach viewers how to create an automated workflow that accepts meeting invitations based on specific criteria, utilizing conditional logic to manage actions effectively.


Chapitres :

  1. Introduction to Automated Workflows
    In complex workflows, it is often necessary to generate different actions based on various criteria. This video focuses on automating the acceptance of meeting invitations that contain a specific keyword from an organizer.
  2. Understanding Conditional Logic
    The example presented illustrates the principle of the 'if' condition, which allows for testing a set of conditions and chaining actions. If the condition is met, specific actions will be executed; otherwise, alternative actions will be taken.
  3. Creating the Automated Flow
    To create the automated flow, you will name it and use the action related to creating an event in Outlook. In the properties, ensure to monitor your calendar and set the frequency for checking new events to one minute, allowing the flow to run almost immediately after receiving an invitation.
  4. Managing Conditions
    All conditional actions are grouped under 'Control'. The basic condition, labeled 'Condition', allows you to insert a double condition. The first condition is based on a specific organizer, which can be selected from dynamic content by clicking the 'See More' button. Enter the email address of the organizer for this flow.
  5. Defining Multiple Conditions
    Add a second condition of the 'and' type, indicating that all listed conditions must be met. This second constraint is based on the subject of the invitation, which must contain the word 'training'.
  6. Configuring Actions Based on Conditions
    Focus on the actions associated with the results of the conditions. Start with the 'Condition Met' part by selecting the action to respond to the invitation. In the properties, identify the item via its ID and associate the action of accepting the invitation while disabling the automatic email sent to the organizer.
  7. Handling Non-Matching Conditions
    In cases where the conditions are not met, add an action to respond with a tentative acceptance, this time leaving the email sending active. Save and test your flow.
  8. Testing the Flow
    To test the flow, access the account associated with the condition and simulate two invitations in the recipient's account where the flow was created. The meetings will appear in your calendar with a pending acceptance status for the first one, and after a few moments, an acceptance status for the invitation meeting that met both criteria.
  9. Conclusion
    Your flow is now functional and correctly handles the configured conditions. The organizer will receive an email only for the pending meeting, confirming that the automation works as intended.

FAQ :

What is a workflow in automation?

A workflow in automation refers to a series of tasks or processes that are executed automatically based on predefined rules and conditions.

How do I create an automated flow in Outlook?

To create an automated flow in Outlook, you need to define the conditions that trigger the flow, specify the actions to be taken, and set the frequency for checking new events.

What does the 'if condition' do in an automated flow?

The 'if condition' allows you to test specific criteria and execute different actions based on whether those criteria are met or not.

What is the purpose of setting a frequency for checking new events?

Setting a frequency for checking new events ensures that the automated flow runs at regular intervals, allowing for timely responses to incoming invitations.

What happens if the conditions in my flow are not met?

If the conditions in your flow are not met, the flow will execute alternative actions, such as sending a tentative acceptance response instead of accepting the invitation.


Quelques cas d'usages :

Automating Meeting Responses

In a corporate environment, an employee can set up an automated flow to accept meeting invitations that contain specific keywords, such as 'training'. This ensures that important meetings are automatically acknowledged, improving response times and reducing manual effort.

Managing Calendar Events

A project manager can use automated flows to monitor their calendar for invitations from key stakeholders. By setting conditions based on the organizer's email and meeting subject, they can streamline their scheduling process and ensure they never miss critical meetings.

Improving Team Collaboration

A team leader can implement an automated flow that responds to meeting invitations based on team members' availability. This helps in coordinating schedules effectively and enhances overall team collaboration.


Glossaire :

workflow

A sequence of processes through which a piece of work passes from initiation to completion.

automate

To use technology to perform tasks without human intervention.

if condition

A logical statement that executes certain actions based on whether a specified condition is true or false.

event in Outlook

A scheduled meeting or appointment created in Microsoft Outlook's calendar.

dynamic content

Content that changes based on user interactions or other variables, often used in automated workflows.

tentative acceptance

A response to a meeting invitation indicating that the recipient may attend but is not yet certain.

condition met

A scenario where the specified criteria in a conditional statement are satisfied.

parameterize

To define parameters or variables that can be adjusted to customize the behavior of a process.

00:00:04
you will often need to generate different actions based on various criteria.
00:00:08
Let's focus here on a flow that will automate the acceptance
00:00:11
of a meeting invitation containing a specific keyword from an organizer.
00:00:16
The example used in this flow is simple
00:00:19
but well illustrates the principle of the if condition
00:00:22
which allows testing a set of conditions and chaining actions.
00:00:26
If the condition is met as well as other actions, otherwise
00:00:31
you will create an automated flow which you will name
00:00:35
using the action related to creating an event in outlook
00:00:44
in the properties indicate monitoring your calendar
00:00:47
and set the frequency of checking for new
00:00:49
events to one minute so that the flow
00:00:51
runs almost immediately after receiving the invitation.
00:00:56
Now let's focus on managing your condition.
00:00:59
All conditional actions are grouped under control. The basic condition.
00:01:04
If in this case is labeled condition,
00:01:07
you will discover in other tutorials. Some other types of conditions.
00:01:12
Once the condition is inserted,
00:01:14
you will see two branches allowing you to perform distinct actions according to
00:01:18
the result of the condition that you will parameterize in the property pane.
00:01:23
You will define a double condition.
00:01:25
The first based on a specific organizer.
00:01:28
This dynamic content associated with the previous action
00:01:31
is available by clicking on the see more button.
00:01:40
Enter the email address of the organizer concerned by this flow,
00:01:44
then add a second condition of the and type
00:01:47
indicating that all listed conditions must be met.
00:01:51
This second constraint is based on the
00:01:52
subject which must contain the word training.
00:01:57
Now focus on the actions associated with the results.
00:02:00
Start with the condition met part by
00:02:02
selecting the action to respond to the invitation
00:02:09
in the properties, identify the item via its id
00:02:14
and associate the action of accepting the invitation
00:02:17
while disabling the automatic email sent to the organizer
00:02:23
in the case where the conditions are not met.
00:02:25
Add again the action to respond by defining a tentative acceptance as the response
00:02:30
this time leaving the email sending active
00:02:34
save and test your flow.
00:02:36
Having access to the account associated
00:02:38
with the condition simulate two invitations
00:02:41
in the recipient's account where you created your flow.
00:02:44
The meetings appear well in your calendar with
00:02:46
a pending acceptance status for the first one
00:02:49
and after a few moments,
00:02:50
an acceptance status for the invitation meeting both criteria.
00:02:54
Your flow is functional and correctly handles the configured condition.
00:03:00
The organizer for their part receives an email only for the pending meeting.
00:03:04
That is perfect.

No elements match your search in this video....
Do another search or back to content !

 

00:00:03
Em fluxos de trabalho mais complexos,
00:00:04
muitas vezes terá de gerar ações diferentes com base em vários critérios.
00:00:08
Vamos focar-nos aqui num fluxo que irá automatizar a aceitação
00:00:11
de um convite de reunião contendo uma palavra-chave específica de um organizador.
00:00:16
O exemplo utilizado neste fluxo é simples
00:00:19
mas ilustra bem o princípio da condição if
00:00:22
que permite testar um conjunto de condições e ações de encadeamento.
00:00:26
Se a condição for cumprida, bem como outras ações, caso contrário
00:00:31
irá criar um fluxo automático que irá nomear
00:00:35
utilizando a ação relacionada com a criação de um evento no outlook
00:00:44
nas propriedades indicar monitorizar o seu calendário
00:00:47
e definir a frequência de verificação de novos
00:00:49
eventos a um minuto para que o fluxo
00:00:51
corre quase imediatamente após receber o convite.
00:00:56
Agora vamos concentrar-nos em gerir a sua condição.
00:00:59
Todas as acções condicionais estão agrupadas sob controlo. A condição básica.
00:01:04
Se, neste caso, estiver rotulado como condição,
00:01:07
irá descobrir noutros tutoriais. Alguns outros tipos de condições.
00:01:12
Uma vez inserida a condição,
00:01:14
verá dois ramos que lhe permitem realizar ações distintas de acordo com
00:01:18
o resultado da condição que irá parametrizar no painel de propriedades.
00:01:23
Vai definir uma condição dupla.
00:01:25
O primeiro com base num organizador específico.
00:01:28
Este conteúdo dinâmico associado à ação anterior
00:01:31
está disponível clicando no botão ver mais.
00:01:40
Introduza o endereço de correio electrónico do organizador envolvido por este fluxo,
00:01:44
em seguida, adicione uma segunda condição do e digite
00:01:47
indicando que todas as condições enumeradas devem ser preenchidas.
00:01:51
Esta segunda restrição baseia-se na
00:01:52
disciplina que deve conter a palavra formação.
00:01:57
Agora concentre-se nas ações associadas aos resultados.
00:02:00
Comece com a condição atendida parte por
00:02:02
selecionar a ação para responder ao convite
00:02:09
nas propriedades, identifique o item através do seu id
00:02:14
e associar a ação de aceitar o convite
00:02:17
ao desativar o e-mail automático enviado ao organizador
00:02:23
no caso de as condições não estarem preenchidas.
00:02:25
Adicione novamente a ação para responder definindo uma aceitação provisória como a resposta
00:02:30
desta vez deixando o envio de correio electrónico activo
00:02:34
salve e teste o seu fluxo.
00:02:36
Ter acesso à conta associada
00:02:38
com a condição simular dois convites
00:02:41
na conta do destinatário onde criou o fluxo.
00:02:44
As reuniões aparecem bem no seu calendário com
00:02:46
um estatuto de aceitação pendente para o primeiro
00:02:49
e depois de alguns instantes,
00:02:50
um estado de aceitação para o convite que satisfaz ambos os critérios.
00:02:54
O seu fluxo está funcional e lida corretamente com a condição configurada.
00:03:00
O organizador, por sua vez, recebe um e-mail apenas para a reunião pendente.
00:03:04
Isso é perfeito.

No elements match your search in this video....
Do another search or back to content !

 

00:00:03
Nei flussi di lavoro più complessi,
00:00:04
spesso è necessario generare azioni diverse in base a vari criteri.
00:00:08
Concentriamoci qui su un flusso che automatizzerà l'accettazione
00:00:11
di un invito a una riunione contenente una parola chiave specifica di un organizzatore.
00:00:16
L'esempio utilizzato in questo flusso è semplice
00:00:19
ma illustra bene il principio della condizione if
00:00:22
che consente di testare una serie di condizioni e di concatenare le azioni.
00:00:26
Se la condizione è soddisfatta così come altre azioni, altrimenti
00:00:31
creerai un flusso automatico a cui darai un nome
00:00:35
utilizzando l'azione relativa alla creazione di un evento in Outlook
00:00:44
nelle proprietà indica il monitoraggio del calendario
00:00:47
e imposta la frequenza di verifica delle nuove
00:00:49
eventi a un minuto in modo che il flusso
00:00:51
viene eseguito quasi subito dopo aver ricevuto l'invito.
00:00:56
Ora concentriamoci sulla gestione della tua condizione.
00:00:59
Tutte le azioni condizionali sono raggruppate sotto controllo. La condizione di base.
00:01:04
Se in questo caso è indicata come condizione,
00:01:07
lo scoprirai in altri tutorial. Alcuni altri tipi di condizioni.
00:01:12
Una volta inserita la condizione,
00:01:14
vedrai due rami che ti permetteranno di eseguire azioni distinte in base a
00:01:18
il risultato della condizione che parametrizzerai nel pannello delle proprietà.
00:01:23
Definirai una doppia condizione.
00:01:25
La prima basata su un organizzatore specifico.
00:01:28
Questo contenuto dinamico è associato all'azione precedente
00:01:31
è disponibile facendo clic sul pulsante Vedi altro.
00:01:40
Inserisci l'indirizzo email dell'organizzatore interessato da questo flusso,
00:01:44
quindi aggiungi una seconda condizione del tipo e
00:01:47
indicando che tutte le condizioni elencate devono essere soddisfatte.
00:01:51
Questo secondo vincolo si basa sul
00:01:52
soggetto che deve contenere la parola formazione.
00:01:57
Ora concentrati sulle azioni associate ai risultati.
00:02:00
Inizia con la condizione soddisfatta in parte per
00:02:02
selezionando l'azione per rispondere all'invito
00:02:09
nelle proprietà, identifica l'articolo tramite il suo id
00:02:14
e associa l'azione di accettazione dell'invito
00:02:17
disattivando l'email automatica inviata all'organizzatore
00:02:23
nel caso in cui le condizioni non siano soddisfatte.
00:02:25
Aggiungete nuovamente l'azione per rispondere definendo come risposta un'accettazione provvisoria
00:02:30
questa volta lasciando attivo l'invio delle email
00:02:34
salva e testa il tuo flusso.
00:02:36
Avere accesso all'account associato
00:02:38
con la condizione simula due inviti
00:02:41
nell'account del destinatario in cui hai creato il flusso.
00:02:44
Le riunioni vengono visualizzate bene nel tuo calendario con
00:02:46
uno stato di accettazione in sospeso per il primo
00:02:49
e dopo pochi istanti,
00:02:50
uno stato di accettazione dell'invito che soddisfa entrambi i criteri.
00:02:54
Il flusso è funzionale e gestisce correttamente la condizione configurata.
00:03:00
L'organizzatore, da parte sua, riceve un'e-mail solo per la riunione in sospeso.
00:03:04
Questo è perfetto.

No elements match your search in this video....
Do another search or back to content !

 

00:00:03
В более сложных рабочих процессах
00:00:04
вам часто придется генерировать разные действия на основе разных критериев.
00:00:08
Давайте сосредоточимся здесь на потоке, который автоматизирует принятие
00:00:11
приглашения на собрание, содержащего определенное ключевое слово от организатора.
00:00:16
Пример, использованный в этом потоке, прост
00:00:19
но хорошо иллюстрирует принцип условия if
00:00:22
которое позволяет тестировать набор условий и объединять действия в цепочку.
00:00:26
Если условие выполнено, а также выполнение других действий, в противном случае
00:00:31
вы создадите автоматизированный поток, который вы назовете
00:00:35
используя действие, связанное с созданием события в Outlook
00:00:44
в свойствах укажите мониторинг вашего календаря
00:00:47
и задайте периодичность проверки новых
00:00:49
события до одной минуты, чтобы поток
00:00:51
запускается почти сразу после получения приглашения.
00:00:56
Теперь давайте сосредоточимся на лечении вашего состояния.
00:00:59
Все условные действия сгруппированы под контролем. Основное условие.
00:01:04
Если в данном случае указано состояние,
00:01:07
вы узнаете об этом в других уроках. Некоторые другие типы условий.
00:01:12
Как только условие будет вставлено,
00:01:14
вы увидите две ветки, позволяющие выполнять различные действия в соответствии с
00:01:18
результат выполнения условия, которое вы параметризуете на панели свойств.
00:01:23
Вы определите двойное условие.
00:01:25
Первое основано на конкретном органайзере.
00:01:28
Это динамический контент, связанный с предыдущим действием
00:01:31
доступно при нажатии на кнопку «Показать больше».
00:01:40
Введите адрес электронной почты организатора, заинтересованного в этом потоке,
00:01:44
затем добавьте второе условие типа «и»
00:01:47
указывающее, что все перечисленные условия должны быть выполнены.
00:01:51
Это второе ограничение основано на
00:01:52
предмет, который должен содержать слово «обучение».
00:01:57
Теперь сосредоточьтесь на действиях, связанных с результатами.
00:02:00
Начните с условия, выполненного по частям
00:02:02
выберите действие для ответа на приглашение
00:02:09
в свойствах идентифицируйте товар по его идентификатору
00:02:14
и свяжите действие с принятием приглашения
00:02:17
отключив автоматическое отправление электронной почты организатору
00:02:23
в случае, если условия не соблюдены.
00:02:25
Добавьте еще раз действие по реагированию, определив в качестве ответа предварительное согласие
00:02:30
на этот раз отправка электронной почты оставлена активной
00:02:34
сохраните и протестируйте свой поток.
00:02:36
Наличие доступа к связанной учетной записи
00:02:38
с условием смоделируйте два приглашения
00:02:41
в учетной записи получателя, где вы создали свой поток.
00:02:44
Встречи хорошо отображаются в вашем календаре с
00:02:46
первое из них находится на стадии принятия
00:02:49
и через несколько мгновений
00:02:50
статус принятия приглашения, отвечающий обоим критериям.
00:02:54
Ваш процесс работает и правильно обрабатывает настроенное условие.
00:03:00
Со своей стороны, организатор получает электронное письмо только о предстоящей встрече.
00:03:04
Это прекрасно.

No elements match your search in this video....
Do another search or back to content !

 

00:00:03
En flujos de trabajo más complejos,
00:00:04
a menudo necesitarás generar diferentes acciones en función de varios criterios.
00:00:08
Centrémonos aquí en un flujo que automatizará la aceptación
00:00:11
de una invitación a una reunión que contiene una palabra clave específica de un organizador.
00:00:16
El ejemplo utilizado en este flujo es sencillo
00:00:19
pero ilustra bien el principio de la condición si
00:00:22
que permite probar un conjunto de condiciones y encadenar acciones.
00:00:26
Si se cumple la condición, así como otras acciones, de lo contrario
00:00:31
crearás un flujo automatizado al que pondrás un nombre
00:00:35
usando la acción relacionada con la creación de un evento en Outlook
00:00:44
en las propiedades, indique la supervisión de su calendario
00:00:47
y establezca la frecuencia de comprobación de si hay nuevos
00:00:49
eventos a un minuto para que el flujo
00:00:51
se ejecuta casi inmediatamente después de recibir la invitación.
00:00:56
Ahora centrémonos en controlar su afección.
00:00:59
Todas las acciones condicionales se agrupan bajo control. La condición básica.
00:01:04
Si en este caso está etiquetada como condición,
00:01:07
lo descubrirás en otros tutoriales. Algunos otros tipos de afecciones.
00:01:12
Una vez insertada la afección,
00:01:14
verá dos ramas que le permitirán realizar distintas acciones de acuerdo con
00:01:18
el resultado de la condición que parametrizará en el panel de propiedades.
00:01:23
Definirá una doble condición.
00:01:25
La primera basada en un organizador específico.
00:01:28
Este contenido dinámico asociado a la acción anterior
00:01:31
está disponible haciendo clic en el botón de ver más.
00:01:40
Introduzca la dirección de correo electrónico del organizador afectado por este flujo,
00:01:44
a continuación, añada una segunda condición del tipo y
00:01:47
indicando que se deben cumplir todas las condiciones enumeradas.
00:01:51
Esta segunda restricción se basa en la
00:01:52
asignatura que debe contener la palabra formación.
00:01:57
Ahora céntrese en las acciones asociadas a los resultados.
00:02:00
Comience con la condición cumplida en parte
00:02:02
seleccionar la acción para responder a la invitación
00:02:09
en las propiedades, identifique el artículo a través de su identificador
00:02:14
y asocie la acción de aceptar la invitación
00:02:17
mientras se desactiva el correo electrónico automático enviado al organizador
00:02:23
en el caso de que no se cumplan las condiciones.
00:02:25
Vuelva a agregar la acción para responder definiendo una aceptación provisional como la respuesta
00:02:30
esta vez dejando activo el envío del correo electrónico
00:02:34
guarda y prueba tu flujo.
00:02:36
Tener acceso a la cuenta asociada
00:02:38
con la condición simula dos invitaciones
00:02:41
en la cuenta del destinatario en la que creaste tu flujo.
00:02:44
Las reuniones aparecen bien en tu calendario con
00:02:46
un estado de aceptación pendiente para la primera
00:02:49
y después de unos instantes,
00:02:50
un estado de aceptación de la invitación que cumple ambos criterios.
00:02:54
Su flujo es funcional y gestiona correctamente la condición configurada.
00:03:00
El organizador, por su parte, recibe un correo electrónico solo para la reunión pendiente.
00:03:04
Eso es perfecto.

No elements match your search in this video....
Do another search or back to content !

 

Mandarine AI: CE QUI POURRAIT VOUS INTÉRESSER

Reminder

Show