Page tree
Skip to end of metadata
Go to start of metadata
Project NameDescriptionInterested Community MembersComments
Document management integration (via CMIS)

Integration with CMIS compatible document repositories - this might involve:

  • Archive files sent to Symphony chats
  • Allow files stored in a document management repository to be selected and shared on a Symphony chat


Maven SDK SamplesRun SDK examples against foundation POD; create Maven Archetype and/or Parent Pom to simplify project's pom definition

ChatMeUpAI chatterbot to have a conversation. https://www.chatbots.org/

TTYLBot holding messages to be delivered later. Useful as Symphony alarm clock and scheduler; bot should allow event/message input and list of pending messages organized by datetime.

Agent WebBot searches the web and returns results in a formatted Symphony message.

SymMailEmail ↔ Symphony BOT

Markdown message formatterAllow to write markdown format in a Symphony chat and submit the formatted version of the message
Proposed during London Meetup
urban-botA bot that resolves acronyms and slang terms by searching on urbandictionary and other configurable sourcesMaurizio Pillitu
offbotA bot to offboard inactive users; the bot can be configured with:
  • A chat room where it can report activities
  • an email address to notify with activities
  • inactivity timeframe (in days or months)

translatorA bot to translate messages, relying on third-party (pluggable) services, such as Google Translate or Microsoft Translate. Stretch goal: a bot can ask to chat users to validate/certify a translation.Maurizio Pillitu, Vincent Gurle
IRC Protocol BridgeA component that "speaks" the IRC protocol outbound and maps it to Symphony equivalents, thereby enabling integration with IRC clients.Comet ☄
Command line interface for SymphonyA command line interface for Symphony, so that chat operations can be scripted.Comet ☄
Travis CI integrationAllow Symphony users to receive notifications from Travis CI, for example when a build completes.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here from TravisCI: https://docs.travis-ci.com/user/notifications/#Webhook-notification


Statuspage.io

Allow Symphony users to receive notifications from Statuspage.io for example, when an incident occurs.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here from Statuspage.io: https://help.statuspage.io/knowledge_base/topics/webhook-notifications



Raygun

Allow Symphony users to receive notifications from Raygun, for example when an error occurs.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://raygun.com/docs/integrations/webhooks



Rainforest QA

Allow Symphony users to receive notifications from Rainforest QA, for example when a test has completed.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: http://support.rainforestqa.com/hc/en-us/articles/203606313-Webhooks



Pingdom

Allow Symphony users to receive notifications from Pingdom, for example when load spikes on your site.


This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://help.pingdom.com/hc/en-us/articles/207081599-Webhooks-Integration



Papertrail

Allow Symphony users to receive notifications from Papertrail, for example when a fault occurs.


This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: http://help.papertrailapp.com/kb/how-it-works/web-hooks/



Pagerduty

Allow Symphony users to receive notifications from Pagerduty, for example when an incident is resolved.


This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://v2.developer.pagerduty.com/docs/webhooks-overview



MailChimp

Allow Symphony users to receive notifications from MailChimp, for example when a campaign ends.


This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: http://kb.mailchimp.com/integrations/api-integrations/how-to-set-up-webhooks



LogEntries

Allow Symphony users to receive notifications from LogEntries, for example when a log is captured due to an error.


This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://docs.logentries.com/docs/webhookalert



HoneyBadger

Allow Symphony users to receive notifications from HoneyBadger, for example when a fault occurs.


This can follow the pattern of other webhook based-bots such as JIRA. See documentation here:http://docs.honeybadger.io/guides/integrations.html#webhook



Heroku

Allow Symphony users to receive notifications from Heroku, such as when a build completes.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://devcenter.heroku.com/articles/deploy-hooks#http-post-hook



HelpScout

Allow Symphony users to receive notifications from HelpScout, such as when a ticket is opened.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: http://developer.helpscout.net/help-desk-api/webhooks/



Groove

Allow Symphony users to receive notifications from Groove, such as when a ticket is opened.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://www.groovehq.com/docs/webhooks



DataDog

Allow Symphony users to receive notifications from DataDog, such as when a usage metric is alerted

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: http://docs.datadoghq.com/integrations/webhooks/



CodeShip

Allow Symphony users to receive notifications from CodeShip, such a build is successfully deployed.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://documentation.codeship.com/basic/getting-started/webhooks/



Cloud66

Allow Symphony users to receive notifications from Cloud66, such a build is successfully deployed.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: http://help.cloud66.com/account-management/account-notifications



CircleCI

Allow Symphony users to receive notifications from CircleCI, such as build is successfully deployed.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://circleci.com/docs/configuration/



Beanstalk

Allow Symphony users to receive notifications from beanstalk, such as when code review is completed.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: http://support.beanstalkapp.com/article/955-modular-webhooks-integration



AppSignal

Allow Symphony users to receive notifications from AppSignal, such as when an error occurs

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: http://docs.appsignal.com/application/integrations/webhooks.html



AirBrake

Allow Symphony users to receive notifications from AirBrake, such as when an exception occurs.

This can follow the pattern of other webhook based-bots such as JIRA. See documentation here: https://airbrake.io/docs/integrations/webhooks/



LinkedIn

Link to, or display a user's LinkedIn profile from within the Symphony UI.

  • Could show your contacts that are on LinkedIn & Symphony and propose a connection request
  • Could notify you when one of your LinkedIn contacts join Symphony


ServiceNow

Allow Symphony users to receive notifications from ServiceNow

This can follow the pattern of other webhook-based bots, such as JIRA. See documentation here: http://wiki.servicenow.com/index.php?title=Outbound_REST_Web_Service#gsc.tab=0

Maurizio Pillitu, Vincent Gurle
Multi-party X-Pod Bot

A bot that emulates multi-party cross-pod by proxying messages between a set of per-pod chat rooms that it manages.

Note: the proxy-bot component within the helpdesk-bot project already does some of this, but is somewhat coupled to the "support helpdesk" use case. The proposed project might involve decoupling just the proxy-bot component then generalising it to any multi-party cross-pod use case.

Peter Monks
  • No labels