Skip to content

Commit 68d0d8c

Browse files
add email notifications callout
1 parent 2aca6f5 commit 68d0d8c

File tree

1 file changed

+6
-1
lines changed
  • docs-v2/pages/workflows/building-workflows

1 file changed

+6
-1
lines changed

docs-v2/pages/workflows/building-workflows/errors.mdx

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
import VideoPlayer from "@/components/VideoPlayer";
2+
import Callout from '@/components/Callout'
23

34
# Handling errors
45

@@ -21,14 +22,18 @@ You can apply conditional logic in code, or using the [If / Else operator](/work
2122

2223
## Error notifications
2324

24-
By default, [Pipedream sends an email](#default-system-emails) when a workflow throws an unhandled error. But you can
25+
By default, [Pipedream sends an email](#default-system-emails) when a workflow throws an unhandled error. But you can:
2526

2627
- Send error notifications to Slack
2728
- Handle errors from one workflow in a specific way
2829
- Fetch errors asynchronously using the REST API, instead of handling the event in real-time
2930

3031
These docs describe the default error behavior, and how to handle custom use cases like these.
3132

33+
<Callout type="info">
34+
Email notifications are sent to the address specified in your [workspace settings](https://pipedream.com/settings/account) under the **Notifications** section. We recommend using a group email address so everyone can monitor workflow errors.
35+
</Callout>
36+
3237
Before you jump into the examples below, remember that all Pipedream workflows are just code. You can always use the built-in error handling logic native to your programming language, for example: using JavaScript's [`try / catch` statement](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch). In the future, Pipedream plans to support this kind of error-handling for built-in actions, as well.
3338

3439
### Default system emails

0 commit comments

Comments
 (0)