Overview
This node manages Microsoft Graph webhook subscriptions specifically for Outlook Groups. It allows users to create, update, delete, and list webhook subscriptions that monitor conversations within Microsoft 365 groups. This is useful for automating workflows triggered by group conversation events, such as receiving notifications when new messages are created.
Practical examples include:
- Creating a subscription to receive real-time notifications when new conversations are started in a specific Microsoft 365 group.
- Updating an existing subscription’s webhook URL or extending its expiration time.
- Deleting obsolete subscriptions to stop receiving notifications.
- Listing all active subscriptions to audit or manage them.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | The URL endpoint that will receive the webhook notifications from Microsoft Graph. |
| Subscription ID | The unique identifier of the subscription to update or delete. |
| Expiration Hours | Duration in hours for how long the subscription should remain active (maximum 4230 hours). |
Output
The node outputs JSON data representing the response from Microsoft Graph API calls related to subscriptions:
- For create and update operations, it returns the subscription object with details such as
id,resource,expirationDateTime, etc. - For delete, it returns a success message confirming deletion along with the deleted subscription ID.
- For list, it returns a collection of all active subscriptions.
- In case of errors (if "Continue On Fail" is enabled), it outputs an error message in JSON format.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Microsoft Graph with permissions to manage subscriptions on Outlook Groups.
- Uses Microsoft Graph API endpoints under
/subscriptionsand/groups/{groupId}/conversations. - The node depends on a helper function to make authenticated HTTP requests to Microsoft Graph.
Troubleshooting
Common issues:
- Invalid or expired API credentials can cause authentication failures.
- Providing an incorrect Group ID or Subscription ID will result in not found errors.
- Setting expiration hours beyond the maximum allowed (4230) may cause API rejections.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Errors returned from Microsoft Graph API are passed through; typical messages include permission denied, invalid resource, or subscription not found.
- If the node throws an error, verify the input parameters and API credentials.
- Use the "Continue On Fail" option to handle errors gracefully and inspect error messages in the output.