Adaptive Card Actions
Performing adaptive card related actions in your Looply workflows
Last updated
Performing adaptive card related actions in your Looply workflows
Last updated
Adaptive Card Actions provide a direct avenue for users to harness the full potential of their Microsoft integration within workflows.
Specifically designed for efficiency, these steps empower users to send, update, or delete Adaptive Cards seamlessly using their integrated Microsoft account and Looply-created apps.
Imagine the ability to notify users of events within your system or process by incorporating Adaptive Card Actions into your workflow. It's a precise, no-nonsense approach to integrating Adaptive Cards that aligns seamlessly with your communication and notification needs.
You can get started configuring your adaptive card action by clicking on a + button in your workflow and selecting the Adaptive Card Action step from the Workflow's toolbox.
You can instruct your workflow to send an adaptive card by using the Card Action dropdown menu and selecting Send.
For every adaptive card action you wish to carry out with Looply, you'll need to define the Microsoft Teams app you want to use to process the action.
Use the Select App dropdown to select which Looply-created Microsoft Teams app you wish to use to dispatch your adaptive card.
You can use the Select New Card dropdown menu to select the Adaptive Card you wish to send to the user.
Additionally, if you haven't created any adaptive cards yet or wish to create a new adaptive card to be used - you can select 'create a new adaptive card' from the dropdown menu. Once selected, a new adaptive card instance will be created and automatically inserted to be used within your adaptive card action.
See Building Adaptive Cards to learn more about creating or editing adaptive cards.
Use the Recipients input field to determine which users should receive the adaptive card.
You can choose to enter your recipients manually or use the dropdown to access data from your event trigger or existing steps.
Tip: When manually entering a recipient, ensure accuracy by using their Microsoft username. This guarantees a seamless connection between Looply and your Microsoft account, ensuring the intended recipient receives the notification promptly.
For example: USERNAME@x3qlj.onmicrosoft.com
You can instruct your workflow to update an adaptive card that was previously dispatched by using the Card Action dropdown menu and selecting Update.
Updating adaptive cards can be useful for displaying new information to your user, for example, if the status of their notification has changed.
To update an adaptive card, you'll first need to select the existing card that was dispatched and should now be updated.
Use the Select Existing Card dropdown menu to select the previous card from your workflow that you want to update.
Use the Select New Card dropdown menu to select the new adaptive card that you wish to replace the previous one.
Additionally, you can use Adaptive Card Action steps to delete previously dispatched adaptive cards to prevent the recipient from being able to view or access them.
This can be useful if you want your notification to expire or no longer require it for a user.
You can instruct your workflow to delete an adaptive card that was previously dispatched by using the Card Action dropdown menu and selecting Delete.
Use the Select Existing Card dropdown menu to select the previous card from your workflow that you want to delete.
When updating or deleting an adaptive card which has been dispatched to a user, you can configure the action to notify the user by toggling the Notify User switch from the configuration options.
This can be useful when you want the recipient to be made aware of the update or deletion of the adaptive card they previously received.
By using the notify user setting, when an update action is processed - the existing card will be deleted and a new one will be dispatched which will ensure the updated notification is pushed to the front of their Teams chat messages. Similarly, when a delete action is processed - a new notification will be issued to the user informing them that the previous message has been deleted.
You can instruct your Looply workflow to accept and handle a response from a user when sending adaptive cards. This is often used in workflows where the recipient is expected to respond to the adaptive card using buttons located on the card. For example, approving or rejecting an event.
When using Adaptive Card Action steps to send a new card to a user, you can add support for accepting a response by toggling the Allow Responses (Teams) or Allow Responses (External) switch.
When you allow responses, the Adaptive Card Action step within your workflow will immediately insert a new Card Response Handler block, followed by separate branches to handle a response from Microsoft Teams (directly from the adaptive card) or an external response.
Card Response Handler blocks are inserted in your workflow when you choose to allow responses from your Adaptive Card send action.
These handlers operate by keeping your workflow in a processing state while they wait for a response to be received. Currently, our Card Response Handlers support responses directly from the adaptive card or alternatively an external response from outside your adaptive card.
The MS Teams Response branch can be used to handle a direct response from Microsoft Teams via your adaptive card. This is most commonly used to process button clicks for specific actions on your adaptive card.
To begin creating your response, click on the placeholder step within the MS Teams Response branch and then select the workflow step you wish to insert here from the Toolbox.
Alternatively, you might want to handle a response or trigger from outside Microsoft Teams relating to the current process. This can be useful if your process has been updated from within a different system or workflow, and you need to update or delete the adaptive card.
To handle an external response within your workflow, click on the placeholder step within the External Response branch and then select the workflow step you wish to insert here from the Toolbox.
