Toast Notifications for Power Apps

Add temporary notification messages that appear briefly to provide feedback. Toasts inform users about completed actions, errors, or important updates without interrupting their workflow.

When to use toast notifications

Toasts are perfect for non-blocking feedback - messages that users should see but don't need to interact with. They appear, deliver their message, and disappear automatically or when dismissed.

Power Apps has a built-in Notify() function for simple notifications. Use PowerLibs toast components when you want more control over styling, positioning, and behavior.

Choose your toast style

Toast Notification

Full-featured toast with emoji, title, message, and action button. Slides in with optional animation.

Best for: Rich feedback messages that might include an undo action. Success messages, warnings, or any notification that benefits from detail.

Settings you can customize:

  • Emoji icon
  • Title and message text
  • Action button text (e.g., "Undo")
  • Position (top-right, bottom-right, etc.)
  • Slide animation on/off
  • Trigger button text

Simple Notification

Minimal notification with primary and secondary text. Clean, straightforward design.

Best for: Quick status updates, simple confirmations, and messages that don't need actions.

Settings you can customize:

  • Primary text (main message)
  • Secondary text (additional detail)
  • Position
  • Trigger button text

Notification with Timer

Notification that automatically disappears after a set duration. No dismiss button needed.

Best for: Success messages and confirmations that should disappear on their own. Keeps the UI clean without user intervention.

Settings you can customize:

  • Primary and secondary text
  • Auto-dismiss duration (milliseconds)
  • Position
  • Trigger button text

Status Notifications

Color-coded notification with status icon. Automatically styled based on type: success (green), error (red), or warning (yellow).

Best for: Clear status feedback where color coding helps users instantly understand success/failure/warning.

Settings you can customize:

  • Status type (success, error, warning)
  • Notification text
  • Position
  • Trigger button text

Implementation steps

1. Select your toast style

Go to Toast and choose the notification style that fits your feedback needs.

Use Status Notifications for operation outcomes (saved, deleted, error). Use Toast Notification when you need an undo action. Use Timed Notification for auto-dismissing confirmations.

2. Configure the notification

Click on your chosen component and use the Settings tab to:

  • Set text - Write clear, concise messages
  • Choose type - (Status) Select success, error, or warning
  • Set duration - (Timed) How long before auto-dismiss
  • Position - Where on screen the toast appears

3. Copy YAML code

Switch to the YAML tab and copy the generated Power Apps code to your clipboard.

4. Paste into Power Apps

Open Power Apps Studio, right-click in the Tree view, and select "Paste code".

Connect toast logic

After pasting, trigger notifications based on your app events:

Show toast on action

// After saving data
Patch(Records, Defaults(Records), NewRecord);
Set(varShowToast, true);
Set(varToastMessage, "Record saved successfully!")

Auto-hide toast with timer

// Show toast and start timer
Set(varShowToast, true);

// In Timer.OnTimerEnd (timer duration = 3000ms)
Set(varShowToast, false)

Show different toast types

// Success
Set(varToastType, "success");
Set(varToastMessage, "Settings saved.");
Set(varShowToast, true)

// Error
Set(varToastType, "error");
Set(varToastMessage, "Failed to save. Please try again.");
Set(varShowToast, true)

// Warning
Set(varToastType, "warning");
Set(varToastMessage, "Connection is slow.");
Set(varShowToast, true)

Undo action

// Store data for undo before deleting
Set(varDeletedRecord, SelectedRecord);
Remove(Records, SelectedRecord);
Set(varShowToast, true);

// On Undo button click
Patch(Records, Defaults(Records), varDeletedRecord);
Set(varShowToast, false)

Show toast on error

// Wrap operation in error handling
If(
    IsError(Patch(Records, Defaults(Records), NewRecord)),
    // Show error toast
    Set(varToastType, "error");
    Set(varToastMessage, "Could not save. Check your connection.");
    Set(varShowToast, true),
    // Show success toast
    Set(varToastType, "success");
    Set(varToastMessage, "Saved!");
    Set(varShowToast, true)
)

Common use cases

Form submission feedback

Show Status Notification (success) when a form submits successfully, or (error) if it fails.

Delete with undo

Use Toast Notification with "Undo" action button when deleting records. Gives users a chance to recover.

Auto-save confirmation

Use Notification with Timer to briefly confirm auto-save without requiring user dismissal.

Connection status

Use Status Notification (warning) to alert users about slow or lost connections.

Settings saved

Use Simple Notification to confirm settings changes with minimal distraction.

Best practices

  • Keep messages short - "Saved!" is better than "Your changes have been successfully saved to the database"
  • Use appropriate types - Green for success, red for errors, yellow for warnings
  • Position consistently - Pick top-right or bottom-right and stick with it
  • Auto-dismiss success - Success messages don't need user action
  • Require action for errors - Important errors might need user acknowledgment
  • Offer undo when possible - For destructive actions, let users reverse mistakes
  • Don't stack too many - One toast at a time is usually enough

Troubleshooting

Toast not appearing

Check that your visibility variable is being set to true. Verify the toast isn't positioned off-screen.

Toast not disappearing

For timed notifications, check your timer is running and the OnTimerEnd resets the visibility variable.

Wrong toast type showing

If using status notifications, verify your type variable is being set correctly ("success", "error", "warning").

Toast appearing behind other elements

Set a high Z-index (100+) on the toast container so it appears above navigation and other UI.

Undo not working

Make sure you're storing the deleted data before removal and that your restore Patch uses the correct data structure.

Toast notifications should be brief and non-blocking. For messages that require user action or confirmation, use a Modal instead.

PowerLibs - 85+ Power Apps Components with Copy-Paste YAML Code