Skip to main content
mFoundry’s notification system keeps every member of your team aware of the activity that matters to them — without flooding inboxes or chat channels with noise they can ignore. You can deliver alerts through in-app banners, email digests, Slack messages, or outbound webhooks, and you can tune each channel per event type so people receive exactly the signal they need.

​
Notification Channels

mFoundry supports four delivery channels. Each can be enabled or disabled independently, and most can be configured at both the organization and the individual project level.

​
Configuring Notification Preferences

Tailor which events reach you and how by following these steps in your account settings.
1

Go to Settings > Notifications

Click Settings in the left sidebar, then select the Notifications tab. You will see a list of event categories alongside toggle controls for each delivery channel.
2

Choose which events trigger notifications

Enable or disable notifications for each event type that mFoundry tracks, including:
  • Project created — a new project is added to your organization
  • Workflow completed — a workflow run finishes successfully or with errors
  • Task assigned — a task is assigned to you or a teammate you follow
  • Member invited — a new person joins your organization or project
  • Integration status changed — a connected integration connects or disconnects
3

Select delivery channels per event type

For each event you have enabled, use the channel checkboxes to choose where the notification appears. You can, for example, send workflow completions to Slack while routing task assignments only to email and in-app.
4

Save your preferences

Click Save Preferences at the bottom of the page. Your settings take effect immediately — the next matching event will be delivered through the channels you selected.

​
Project-Level Notifications

Organization owners and admins can set default notification rules that apply to all members across the organization. These org-wide defaults act as a baseline: they ensure everyone is at least notified about critical events such as integration failures or security-related changes. Individual members can override these defaults on a per-project basis. To do this, navigate to the specific project, open Project Settings > Notifications, and adjust the toggles to match your preferred channels and event types. Your project-level settings take precedence over the org-wide defaults for that project only, leaving other projects unaffected.
For teams with advanced alerting requirements — such as routing critical workflow failures to an on-call system like PagerDuty — use mFoundry’s webhook channel to push structured event payloads to any HTTPS endpoint. See the Webhooks configuration guide to learn how to set up signatures, retries, and delivery logging.