Learn how to use the “Notification” node in an App Connect flow to create notification cards. The Notification node enables you to create a notification card that is sent when certain conditions occur. For instance, you could create a card to be notified when an event in Eventbrite has been created, so that you are prompted/reminded to complete other tasks that might be required for the event. Or you might want to be notified when a task with a specific due date is raised in Asana so that you can complete it on time. Notifications are displayed in the Notifications tab of the App Connect UI for reference. The notification card can also contain automated actions for you to trigger, such as sending an email to your team, or creating a task in another application.

Note: When you stop a running flow, any notifications that were generated for that flow are removed from the Notifications tab.

Follow the steps below to learn how easy it is to use the “Notification” node in an App Connect flow to create notification cards.

First, find or create everything you need:

  • An App Connect subscription.
  • The user names and passwords for the accounts that you want to access (if you haven’t already connected App Connect to your accounts).
    Note: You can connect to your accounts on the Applications tab on the App Connect Catalog page, or you can connect as you add each application to your flow.
    Some applications need some extra information to be able to connect to App Connect; if you need help finding this info, see the “How to” guides for apps.

Next, create your flow:

(App Connect automatically saves your changes as you go. If you move away from the flow at any point, the flow is saved as a draft flow that you can come back to later.)

  1. Log in to App Connect.
  2. From the Dashboard, click New > Event-driven flow. (You can also include a notification node in a flow for an API, but this tutorial will assume that you’re creating an event-driven flow.)
  3. Enter a name that identifies the purpose of your flow.
  4. Select your first application (source), then select the event that’ll trigger the actions in the rest of your flow.
    For some trigger events, you might have to provide some info, like the name of an event or list that you’re expecting to be updated.
  5. Click (+) > Toolbox .
  6. Select the Notification node.
  7. Provide a name for your notification, and, optionally, add a description.
  8. At this point, you can open the options menu [⋮] in the banner and click Start flow. However, why not try adding a user action?
  9. To add a user action, click (+) Add user action.

    The User actions dialog box opens.

  10. In the Button label field, provide a name for your button or user action.
    Note: You can optionally add up to three user action buttons to the notification card.
  11. Next, we need to configure the user action. To do this, close the User actions palette and click the (+) icon next to the user action you just added.

  12. Now you need to choose the application that you want the user action to use. For instance, you might want a button that allows you to send an email to your team from your Gmail account. So in this case, you would select the Gmail application.
  13. Add a suitable action to your flow.
  14. Configure your target application in the usual way, mapping the data that you want to transfer from your source application.
  15. From the banner, open the options menu [⋮] and click Start flow. Then click Dashboard to exit the flow.

Finally, test your flow:

  1. Trigger the action you selected to start your event-driven flow.
  2. From the Notifications tab in the App Connect UI, open the notification card.
  3. Click the button in the card to trigger the user action that you configured.

Other resources

Using the Notification node with an If node

Learn how easy it is to create an event-driven flow in App Connect Designer to introduce user actions within a flow.

Using the Notification & Situation detector nodes

Learn how easy it is to create an event-driven flow in App Connect Designer to detect recurring situations.

If you can’t find what you want, or have comments about this tutorial, please either add comments to the bottom of this page or .

Join The Discussion

Your email address will not be published. Required fields are marked *