Difference between revisions of "Feature:Incoming notifications / (web)hooks"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
* Email/IMAP to channel/storage. Would check for emails and parse one or all of sender/recipient/subject/text in order to trigger extracting information and/or post/store to channel/storage. | * Email/IMAP to channel/storage. Would check for emails and parse one or all of sender/recipient/subject/text in order to trigger extracting information and/or post/store to channel/storage. | ||
* Webpage change tracking to channel/storage (check regularly if content on a page changed) | * Webpage change tracking to channel/storage (check regularly if content on a page changed) | ||
| + | * RemoteStorage resource change to channel/storage | ||
=== Notes === | === Notes === | ||
* [GitHub] Apparently it's now possible to define a single hook for all activities within an organization: https://developer.github.com/changes/2014-12-03-preview-the-new-organization-webhooks-api/ — that means we might be able to set that once per API/OAuth call and have a single catcher for all GitHub-related things (no more forgetting to configure channel notifications for new repos e.g.). Also, notifications for not just commits, but other activities as well. | * [GitHub] Apparently it's now possible to define a single hook for all activities within an organization: https://developer.github.com/changes/2014-12-03-preview-the-new-organization-webhooks-api/ — that means we might be able to set that once per API/OAuth call and have a single catcher for all GitHub-related things (no more forgetting to configure channel notifications for new repos e.g.). Also, notifications for not just commits, but other activities as well. | ||
Revision as of 14:08, 7 December 2014
Summary
Features
Sockethub Butlers
- Incoming Webhook (usually HTTP POST) to channel/storage
- Data formats and message rendering for known hooks/services
- Vanilla hook with defined message format and plain/common rendering for custom services
- RSS feed to channel/storage (detect known types, e.g. MediaWiki recent-changes feed)
- Bitcoin wallet transactions to channel/storage
- Email/IMAP to channel/storage. Would check for emails and parse one or all of sender/recipient/subject/text in order to trigger extracting information and/or post/store to channel/storage.
- Webpage change tracking to channel/storage (check regularly if content on a page changed)
- RemoteStorage resource change to channel/storage
Notes
- [GitHub] Apparently it's now possible to define a single hook for all activities within an organization: https://developer.github.com/changes/2014-12-03-preview-the-new-organization-webhooks-api/ — that means we might be able to set that once per API/OAuth call and have a single catcher for all GitHub-related things (no more forgetting to configure channel notifications for new repos e.g.). Also, notifications for not just commits, but other activities as well.
