Outlook Groups Subscription icon

Outlook Groups Subscription

Manage Microsoft Graph subscriptions for Outlook Groups

Actions3

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 changes in group conversations, such as new messages or updates.

Practical examples include:

  • Creating a subscription to receive notifications when new conversations are created in a specific Microsoft 365 group.
  • Updating an existing subscription’s expiration time or notification URL.
  • Deleting a subscription that is no longer needed.
  • Listing all active subscriptions to manage or audit them.

Properties

Name Meaning
Subscription ID The ID of the subscription to update or delete.

(Note: For the "Delete Subscription" operation, only the "Subscription ID" property is required.)

Output

The node outputs JSON data representing the result of the performed operation:

  • Create Subscription: Returns the full subscription object as received from Microsoft Graph API, including details like subscription ID, resource, expiration time, etc.
  • Update Subscription: Returns the updated subscription object.
  • Delete Subscription: Returns a JSON object confirming success with fields:
    • success: true
    • message: Confirmation string including the deleted subscription ID
    • subscriptionId: The ID of the deleted subscription
  • List Subscriptions: Returns a JSON object containing all active subscriptions.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for Microsoft Graph API access configured in n8n.
  • Uses Microsoft Graph API endpoints related to subscriptions (/subscriptions).
  • The node depends on proper permissions granted to the API key to manage subscriptions on Outlook Groups.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication errors.
    • Providing an incorrect subscription ID for update or delete operations will result in not found errors.
    • Exceeding the maximum allowed expiration hours (4230) may cause validation errors.
    • Network or permission issues can prevent successful API calls.

  • Error messages:

    • Errors returned from Microsoft Graph API are passed through; typical messages include unauthorized access, invalid subscription ID, or bad request due to malformed parameters.
    • If the node is set to continue on fail, errors are returned in the output JSON under an error field.

  • Resolutions:

    • Verify API credentials and permissions.
    • Double-check subscription IDs before update or delete.
    • Ensure expiration hours are within allowed limits.
    • Check network connectivity and Microsoft Graph service status.

Links and References

Discussion