2013-07-29 23:03:31 +02:00
{% extends "zerver/portico.html" %}
2013-02-06 20:25:04 +01:00
{# API information page #}
2015-09-24 01:35:21 +02:00
{% block os_announcement %}
{% if zulip_com %}
< div class = "os-headline-container" >
< img src = "/static/images/logo/zballoon.png" class = "os-illustration" alt = "Zulip balloon" / >
< div class = "main-headline-text" >
< span class = "tagline os-tagline" >
Zulip has been released as open source software!
< / span >
< span class = "footnote os-footnote" >
Read the < a href = "https://blogs.dropbox.com/tech/2015/09/open-sourcing-zulip-a-dropbox-hack-week-project" target = "_blank" > announcement< / a > or go to < a href = "https://www.zulip.org" target = "_blank" > the Zulip open source project website< / a > .
< / span >
< / div >
< / div >
{% endif %}
{% endblock %}
2013-02-06 20:25:04 +01:00
{% block portico_content %}
2013-10-21 21:19:31 +02:00
< div class = "portico-page-header" > < a href = "#" > < i class = "icon-vector-gears portico-page-header-icon" > < / i > Integrations< / a > < / div >
2016-04-11 20:15:23 +02:00
< p class = "portico-large-text" > With Zulip integrations, your team
can stay up-to-date on code changes, issue tickets, build system
results, tweets about your project, and much more.< / p >
< p > Many of these integrations require creating a Zulip bot. You
can do so on your < a href = "/#settings" > Zulip settings page< / a > . Be
sure to note its username and API key.< / p >
< p > If an integration you want isn't available yet, you
2016-04-30 01:00:06 +02:00
can < a href = "http://zulip.readthedocs.io/en/latest/integration-guide.html" > contribute
2016-04-11 20:15:23 +02:00
an integration< / a >
or < a href = "https://github.com/zulip/zulip/issues/new" > open an
issue on GitHub< / a > and tag it with the "integrations" label (so
you can get notified when that integration becomes available).< / p >
2013-10-30 00:11:56 +01:00
2013-10-21 21:19:31 +02:00
< div id = "integration-instruction-block" class = "integration-instruction-block" >
< a href = "#" id = "integration-list-link" > < i class = "icon-vector-circle-arrow-left" > < / i > Back to list< / a >
< / div >
< div class = "integration-lozenges" >
2013-11-18 22:21:31 +01:00
< div class = "integration-lozenge integration-asana" >
< a class = "integration-link integration-asana" href = "#asana" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/asana.png" alt = "Asana logo" / >
2013-11-18 22:21:31 +01:00
< span class = "integration-label" > Asana< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-basecamp" >
< a class = "integration-link integration-basecamp" href = "#basecamp" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/basecamp.png" alt = "Basecamp logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Basecamp< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-beanstalk" >
< a class = "integration-link integration-beanstalk" href = "#beanstalk" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/beanstalk.png" alt = "Beanstalk logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Beanstalk< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-bitbucket" >
< a class = "integration-link integration-bitbucket" href = "#bitbucket" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/bitbucket.png" alt = "Bitbucket logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Bitbucket< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-capistrano" >
< a class = "integration-link integration-capistrano" href = "#capistrano" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/capistrano.png" alt = "Capistrano logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Capistrano< / span >
< / a >
2016-05-09 19:59:33 +02:00
< / div > < div class = "integration-lozenge integration-circleci" >
< a class = "integration-link integration-circleci" href = "#circleci" >
< img class = "integration-logo" src = "/static/images/integrations/logos/circleci.png" alt = "CircleCI logo" / >
< span class = "integration-label" > CircleCI< / span >
< / a >
2013-10-21 21:19:31 +02:00
< / div >
< div class = "integration-lozenge integration-codebase" >
< a class = "integration-link integration-codebase" href = "#codebase" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/codebase.png" alt = "Codebase logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Codebase< / span >
< / a >
< / div >
2016-04-11 22:32:07 +02:00
< div class = "integration-lozenge integration-codeship" >
< a class = "integration-link integration-codeship" href = "#codeship" >
< img class = "integration-logo" src = "/static/images/integrations/logos/codeship.png" alt = "Codeship logo" / >
< span class = "integration-label" > Codeship< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-deskcom" >
< a class = "integration-link integration-deskcom" href = "#deskcom" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/deskcom.png" alt = "Desk.com logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Desk.com< / span >
< / a >
< / div >
2013-12-04 22:35:38 +01:00
{% if email_integration_enabled %}
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-email" >
< a class = "integration-link integration-email" href = "#email" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/email.png" alt = "email" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Email< / span >
< / a >
< / div >
2013-12-04 22:35:38 +01:00
{% endif %}
2013-11-09 02:05:27 +01:00
< div class = "integration-lozenge integration-freshdesk" >
< a class = "integration-link integration-freshdesk" href = "#freshdesk" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/freshdesk.png" alt = "Freshdesk logo" / >
2013-11-09 02:05:27 +01:00
< span class = "integration-label" > Freshdesk< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-git" >
< a class = "integration-link integration-git" href = "#git" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/git.png" alt = "Git logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Git< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-github" >
< a class = "integration-link integration-github" href = "#github" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/github.png" alt = "Github logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > GitHub< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-hubot" >
< a class = "integration-link integration-hubot" href = "#hubot" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/hubot.png" alt = "Hubot logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Hubot< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-jenkins" >
< a class = "integration-link integration-jenkins" href = "#jenkins" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/jenkins.png" alt = "Jenkins logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" style = "padding-top: 0px; padding-bottom: 0px;" > Jenkins< / span >
< span class = "integration-label-secondary" > (or Hudson)< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-jira" >
< a class = "integration-link integration-jira" href = "#jira" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/jira.png" alt = "JIRA logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" style = "padding-top: 0px; padding-bottom: 0px;" > JIRA< / span >
< span class = "integration-label-secondary" > (hosted or v5.2+)< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-jira-plugin" >
< a class = "integration-link integration-jira" href = "#jira-plugin" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/jira.png" alt = "JIRA logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" style = "padding-top: 0px; padding-bottom: 0px;" > JIRA< / span >
< span class = "integration-label-secondary" > (locally installed)< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-mercurial" >
< a class = "integration-link integration-mercurial" href = "#mercurial" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/mercurial.png" alt = "Mercurial logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Mercurial (hg)< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-nagios" >
< a class = "integration-link integration-nagios" href = "#nagios" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/nagios.png" alt = "Nagios logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Nagios< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-newrelic" >
< a class = "integration-link integration-newrelic" href = "#newrelic" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/newrelic.png" alt = "New Relic logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > New Relic< / span >
< / a >
< / div >
2015-09-30 09:24:56 +02:00
< div class = "integration-lozenge integration-pagerduty" >
< a class = "integration-link integration-pagerduty" href = "#pagerduty" >
< img class = "integration-logo" src = "/static/images/integrations/logos/pagerduty.png" alt = "Pagerduty logo" / >
< span class = "integration-label" > Pagerduty< / span >
< / a >
< / div >
2013-12-05 22:31:37 +01:00
< div class = "integration-lozenge integration-perforce" >
< a class = "integration-link integration-perforce" href = "#perforce" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/perforce.png" alt = "Perforce logo" / >
2013-12-05 22:31:37 +01:00
< span class = "integration-label" > Perforce< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-phabricator" >
< a class = "integration-link integration-phabricator" href = "#phabricator" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/phabricator.png" alt = "Phabricator logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Phabricator< / span >
< / a >
< / div >
2016-03-14 22:12:46 +01:00
< div class = "integration-lozenge integration-pingdom" >
< a class = "integration-link integration-pingdom" href = "#pingdom" >
< img class = "integration-logo" src = "/static/images/integrations/logos/pingdom.png" alt = "Pingdom logo" / >
< span class = "integration-label" > Pingdom< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-pivotal" >
< a class = "integration-link integration-pivotal" href = "#pivotal" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/pivotal.png" alt = "Pivotal logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Pivotal Tracker< / span >
< / a >
< / div >
2013-12-24 04:46:59 +01:00
< div class = "integration-lozenge integration-puppet" >
< a class = "integration-link integration-puppet" href = "#puppet" >
< img class = "integration-logo" src = "/static/images/integrations/logos/puppet.png" alt = "Puppet logo" / >
< span class = "integration-label" > Puppet< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-redmine" >
< a class = "integration-link integration-redmine" href = "#redmine" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/redmine.png" alt = "Redmine logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Redmine< / span >
< / a >
< / div >
2014-01-02 19:02:17 +01:00
< div class = "integration-lozenge integration-rss" >
< a class = "integration-link integration-rss" href = "#rss" >
< img class = "integration-logo" src = "/static/images/integrations/logos/rss.png" alt = "RSS logo" / >
< span class = "integration-label" > RSS< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-stash" >
< a class = "integration-link integration-stash" href = "#stash" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/stash.png" alt = "Stash logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Stash< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-subversion" >
< a class = "integration-link integration-subversion" href = "#subversion" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/subversion.png" alt = "Subversion logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Subversion< / span >
< / a >
< / div >
2016-04-28 15:46:00 +02:00
< div class = "integration-lozenge integration-taiga" >
< a class = "integration-link integration-taiga" href = "#taiga" >
< img class = "integration-logo" src = "/static/images/integrations/logos/taiga.png" alt = "Taiga logo" / >
< span class = "integration-label" > Taiga< / span >
< / a >
< / div >
2016-04-21 19:18:41 +02:00
< div class = "integration-lozenge integration-teamcity" >
< a class = "integration-link integration-teamcity" href = "#teamcity" >
< img class = "integration-logo" src = "/static/images/integrations/logos/teamcity.png" alt = "Teamcity logo" / >
< span class = "integration-label" > Teamcity< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-trac" >
< a class = "integration-link integration-trac" href = "#trac" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/trac.png" alt = "Trac logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Trac< / span >
< / a >
< / div >
2016-04-09 04:52:14 +02:00
< div class = "integration-lozenge integration-travis" >
< a class = "integration-link integration-travis" href = "#travis" >
< img class = "integration-logo" src = "/static/images/integrations/logos/travis.png" alt = "Travis CI logo" / >
< span class = "integration-label" > Travis CI< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< div class = "integration-lozenge integration-trello" >
< a class = "integration-link integration-trello" href = "#trello" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/trello.png" alt = "Trello logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > trello< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-twitter" >
< a class = "integration-link integration-twitter" href = "#twitter" >
2013-12-17 17:37:28 +01:00
< img class = "integration-logo" src = "/static/images/integrations/logos/twitter.png" alt = "Twitter logo" / >
2013-10-21 21:19:31 +02:00
< span class = "integration-label" > Twitter< / span >
< / a >
< / div >
2016-03-25 17:19:18 +01:00
< div class = "integration-lozenge integration-yo-app" >
< a class = "integration-link integration-yo-app" href = "#yo-app" >
< img class = "integration-logo" src = "/static/images/integrations/logos/yo-app.png" alt = "Yo App logo" / >
< span class = "integration-label" > Yo App< / span >
< / a >
< / div >
2014-01-13 19:25:57 +01:00
< div class = "integration-lozenge integration-zendesk" >
< a class = "integration-link integration-zendesk" href = "#zendesk" >
< img class = "integration-logo" src = "/static/images/integrations/logos/zendesk.png" alt = "Zendesk logo" / >
< span class = "integration-label" > Zendesk< / span >
< / a >
< / div >
2013-10-21 21:19:31 +02:00
< / div >
2016-02-23 21:04:12 +01:00
< div class = "portico-page-header extra" id = "hubot-integrations" > < a href = "#" > < i class = "icon-vector-gears portico-page-header-icon" > < / i > Integrations available via Hubot< / a > < / div >
< p class = "portico-large-text extra" > The official < a class = "integration-link integration-hubot" href = "#hubot" > < span class = "integration-label" > Hubot< / span > < / a >
integration provides an extension point for additional Zulip integrations. < / p > < p class = "portico-large-text extra" > A non-comprehensive list of integrations available through
< a class = "integration-link integration-hubot" href = "#hubot" > < span class = "integration-label" > Hubot< / span > < / a > follows below:< / p >
< div class = "integration-lozenges" >
< div class = "integration-lozenge integration-assembla" >
< a class = "integration-link integration-assembla" href = "https://github.com/hubot-scripts/hubot-assembla" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/assembla.png" alt = "Assembla logo" / >
< span class = "integration-label" > Assembla< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-bonusly" >
< a class = "integration-link integration-bonusly" href = "https://github.com/hubot-scripts/hubot-bonusly" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/bonusly.png" alt = "Bonusly logo" / >
< span class = "integration-label" > Bonusly< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-chartbeat" >
< a class = "integration-link integration-chartbeat" href = "https://github.com/hubot-scripts/hubot-chartbeat" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/chartbeat.png" alt = "Chartbeat logo" / >
< span class = "integration-label" > Chartbeat< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-darksky" >
< a class = "integration-link integration-darksky" href = "https://github.com/hubot-scripts/hubot-darksky" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/darksky.png" alt = "Dark Sky logo" / >
< span class = "integration-label" > Dark Sky< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-hangouts" >
< a class = "integration-link integration-hangouts" href = "https://github.com/hubot-scripts/hubot-google-hangouts" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/hangouts.png" alt = "Hangouts logo" / >
< span class = "integration-label" > Hangouts< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-instagram" >
< a class = "integration-link integration-instagram" href = "https://github.com/hubot-scripts/hubot-instagram" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/instagram.png" alt = "Instagram logo" / >
< span class = "integration-label" > Instagram< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-mailchimp" >
< a class = "integration-link integration-mailchimp" href = "https://github.com/hubot-scripts/hubot-mailchimp" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/mailchimp.png" alt = "MailChimp logo" / >
< span class = "integration-label" > MailChimp< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-translate" >
< a class = "integration-link integration-translate" href = "https://github.com/hubot-scripts/hubot-google-translate" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/translate.png" alt = "Google Translate logo" / >
< span class = "integration-label" > Translate< / span >
< / a >
< / div >
< div class = "integration-lozenge integration-youtube" >
< a class = "integration-link integration-youtube" href = "https://github.com/hubot-scripts/hubot-youtube" target = "_blank" >
< img class = "integration-logo" src = "/static/images/integrations/logos/youtube.png" alt = "YouTube logo" / >
< span class = "integration-label" > YouTube< / span >
< / a >
< / div >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "integration-instructions-group" >
2013-11-18 22:21:31 +01:00
< div id = "asana" class = "integration-instructions" >
< p > Get Zulip notifications for your Asana tasks!< / p >
< p > First, create the stream you'd like to use for Asana notifications, and
subscribe all interested parties to this stream. We recommend the
name < code > asana< / code > .< / p >
< p > Next, on your < a href = "/#settings" target = "_blank" > Zulip settings
page< / a > , create an Asana bot. Please note the bot name and API key.< / p >
< p > Then:< / p >
< ol >
< li >
< p > Download and install our < a href = "/api" > Python bindings< / a > on the
server where the Asana mirroring script will live. The Asana
integration will be installed to a location
like < code > /usr/local/share/zulip/integrations/asana/< / code > .< / p >
< / li >
< li >
< p > Visit your < a href = "https://app.asana.com/-/account_api" > Asana
account settings page< / a > and retrieve your API key.< / p >
2013-12-04 22:01:10 +01:00
< p > Edit < code > asana/zulip_asana_config.py< / code > and
change the following lines to configure the integration:< / p >
< div class = "codehilite" >
< pre >
< span class = "n" > ASANA_API_KEY< / span > < span class = "o" > =< / span > < span class = "s" > 0123456789abcdef0123456789abcdef< / span >
< span class = "n" > ZULIP_USER< / span > < span class = "o" > =< / span > < span class = "s" > "asana-bot@example.com"< / span >
< span class = "n" > ZULIP_API_KEY< / span > < span class = "o" > =< / span > < span class = "s" > "0123456789abcdef0123456789abcdef"< / span >
{% if api_site_required %}< span class = "n" > ZULIP_SITE< / span > < span class = "o" > =< / span > < span class = "s" > "{{ external_api_uri }}"< / span > {% endif %}< / pre >
< / div >
2013-11-18 22:21:31 +01:00
< p > If you are using a stream other than < code > asana< / code > ,
set < code > ZULIP_STREAM_NAME< / code > to the chosen stream name.< / p >
< / li >
< li >
< p > Test your configuration by running the mirror with < code > python
asana/zulip_asana_mirror< / code > . It will print some informational
messages and process any recently created or completed tasks.< / p >
< / li >
< li >
< p > This mirror is intended to be a long-running processing and should be
hooked into your infrastructure for keeping services running (for
example, auto-restarting through < code > supervisord< / code > ).< / p >
< p > Please
2015-09-29 06:17:08 +02:00
contact < a href = "mailto:zulip-devel@googlegroups.com?subject=Asana%20integration%20question" > zulip-devel@googlegroups.com< / a >
2013-11-18 22:21:31 +01:00
if you'd like assistance with maintaining this integration.
< / p >
< / li >
< / ol >
< p > < b > Congratulations! You're done!< / b > < br / > When team members create and
complete tasks in Asana, you'll get a Zulip notification that looks like
this:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/asana/001.png" / >
2013-11-18 22:21:31 +01:00
< / div >
< div id = "basecamp" class = "integration-instructions" >
2013-08-30 21:55:36 +02:00
< p > First, create the stream you'd like to use for Basecamp notifications,
and subscribe all interested parties to this stream. We recommend the
name < code > basecamp< / code > .< / p >
< p > Next, download and install our < a href = "/api" > Python
bindings and example scripts< / a > on the computer you'd like to run this mirroring script from.< / p >
< p > You will need your Basecamp account ID. You can find it as a sequence of numbers in the URL when you log in:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/basecamp/001.png" / >
2013-08-30 21:55:36 +02:00
< p > Edit the Basecamp and Zulip credentials in < code > integrations/basecamp/zulip_basecamp_config.py< / code > using
2013-11-18 22:57:55 +01:00
your favorite editor:< / p >
2013-08-30 21:55:36 +02:00
< div class = "codehilite" >
< pre > < span class = "n" > BASECAMP_ACCOUNT_ID< / span > < span class = "o" > =< / span > < span class = "s" > "1234567"< / span >
< span class = "n" > BASECAMP_USERNAME< / span > < span class = "o" > =< / span > < span class = "s" > "foo@example.com"< / span >
< span class = "n" > BASECAMP_PASSWORD< / span > < span class = "o" > =< / span > < span class = "s" > "p455w0rd"< / span >
< span class = "n" > ZULIP_USER< / span > < span class = "o" > =< / span > < span class = "s" > "basecamp-bot@example.com"< / span >
2013-12-04 21:58:45 +01:00
< span class = "n" > ZULIP_API_KEY< / span > < span class = "o" > =< / span > < span class = "s" > "0123456789abcdef0123456789abcdef"< / span >
{% if api_site_required %}< span class = "n" > ZULIP_SITE< / span > < span class = "o" > =< / span > < span class = "s" > "{{ external_api_uri }}"< / span > {% endif %}< / pre >
2013-08-30 21:55:36 +02:00
< / div >
< p > Before your first run of the script, you may optionally choose to
configure it to mirror some number of hours of Basecamp activity:< / p >
< div class = "codehilite" >
< pre > < span class = "n" > BASECAMP_INITIAL_HISTORY_HOURS< / span > < span class = "o" > =< / span > < span class = "s" > 10< / span > < / pre >
< / div >
< p > Now, simply run the < code > api/integrations/basecamp/zulip_basecamp_mirror< / code > script.
If needed, this script may be restarted, and it will automatically resume from when
it was last running.< / p >
< p > < b > Congratulations! You're done!< / b > < br / > Whenever you create a new project,
calendar event, comment, message, or more, you'll get a notification in your selected stream
2013-11-18 22:57:55 +01:00
with the project or calendar as the topic.< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/basecamp/002.png" / >
2013-08-30 21:55:36 +02:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "beanstalk" class = "integration-instructions" >
2013-08-26 22:58:16 +02:00
< p > Zulip supports both SVN and Git notifications from Beanstalk.< / p >
< p > First, create the stream < code > commits< / code > and subscribe all
interested parties to this stream.< / p >
< p > Next, in the Beanstalk web application, go to the Setup page and choose the Integrations tab.
2013-05-29 17:55:59 +02:00
Choose the < code > Webhooks< / code > integration from the list presented. Make sure to replace the < code > @< / code > in the bot's email address with < code > %40< / code > ,
2013-04-02 23:31:48 +02:00
as Beanstalk's website will incorrectly refuse to parse a username containing a < code > @< / code > .< / p >
2013-04-01 23:57:42 +02:00
2013-12-04 20:57:44 +01:00
< p > In the URL field, enter < code > {{ external_uri_scheme }}bot_email:bot_api_key@{{ external_api_path }}/v1/external/beanstalk< / code > :< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/beanstalk/001.png" / >
2013-04-01 23:57:42 +02:00
< p > < b > Congratulations! You're done!< / b > < br / > Whenever you do a
deployment, you'll get an automated notification that looks like
this:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/beanstalk/002.png" / >
2013-04-01 23:57:42 +02:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "bitbucket" class = "integration-instructions" >
2013-08-26 22:58:16 +02:00
2013-09-03 18:00:32 +02:00
< p > Zulip supports both Git and Mercurial notifications from Bitbucket.< / p >
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for Bitbucket notifications,
and subscribe all interested parties to this stream. The integration will
use the default stream < code > commits< / code > if no stream is supplied in the
hook; you still need to create the stream even if you are using this
default.< / p >
2013-09-03 18:00:32 +02:00
< p > Next, from your repository's web page, go to the Administration page and choose Hooks on the left-hand side.
2013-08-16 02:35:45 +02:00
Choose the < code > POST< / code > hook from the list presented and click "Add hook." Make sure to replace the < code > @< / code > in the bot's email address with < code > %40< / code > ,
as Bitbucket will not execute the hook if the username contains a < code > @< / code > .< / p >
2013-12-04 20:57:44 +01:00
< p > In the URL field, enter < code > {{ external_uri_scheme }}bot_email:bot_api_key@{{ external_api_path }}/v1/external/bitbucket< / code > :< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/bitbucket/001.png" / >
2013-08-16 02:35:45 +02:00
2013-08-26 22:58:16 +02:00
< p > By default, notifications are sent to the < code > commits< / code > stream.
To send notifications to a different stream,
append < code style = "white-space: nowrap;" > ?stream=stream_name< / code > to
the URL.< / p >
2013-08-21 19:10:22 +02:00
2013-08-16 02:35:45 +02:00
< p > < b > Congratulations! You're done!< / b > < br / > Whenever you push code to your repository,
you'll get an automated notification that looks like this:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/bitbucket/002.png" / >
2013-08-16 02:35:45 +02:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "capistrano" class = "integration-instructions" >
2013-03-19 21:22:50 +01:00
< p > First, download and install our < a href = "/api" > Python
bindings and example scripts< / a > on your Capistrano server.
2013-08-07 17:52:53 +02:00
Once you've done that, you'll use the < code > zulip-send< / code >
2013-03-19 21:22:50 +01:00
utility to notify you when certain events happen.< / p >
2013-07-10 22:31:14 +02:00
< p > Here's some example code for sending a Zulip notification
2013-03-19 21:22:50 +01:00
after a deployment has completed:< / p >
2013-03-26 18:12:00 +01:00
< div class = "codehilite" > < pre > < span class = "n" > after< / span > < span class = "s1" > 'deploy'< / span > < span class = "p" > ,< / span > < span class = "s1" > 'notify:humbug'< / span >
2013-03-19 21:22:50 +01:00
< span class = "n" > namespace< / span > < span class = "ss" > :notify< / span > < span class = "k" > do< / span >
2013-07-10 22:31:14 +02:00
< span class = "n" > desc< / span > < span class = "s2" > "Post a message to Zulip that we've deployed"< / span >
2013-03-19 21:22:50 +01:00
< span class = "n" > task< / span > < span class = "ss" > :humbug< / span > < span class = "k" > do< / span >
2013-07-10 22:31:14 +02:00
< span class = "c1" > # this will post to Zulip as the user defined in
2013-08-07 17:36:46 +02:00
# ~/.zuliprc if you omit --user and --api-key< / span >
2013-08-07 17:52:53 +02:00
< span class = "n" > run_locally< / span > < span class = "s2" > "echo ':beers: I just deployed to < / span > < span class = "si" > #{< / span > < span class = "n" > stage< / span > < span class = "si" > }< / span > < span class = "s2" > ! :beers:' | zulip-send \
2013-05-29 17:55:59 +02:00
--user capistrano-bot@example.com --api-key a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5 \
2013-12-04 21:58:45 +01:00
{% if api_site_required %} --site={{ external_api_uri }} \
{% endif %} --stream commits --subject deployments || true"< / span >
2013-03-19 21:22:50 +01:00
< span class = "k" > end< / span >
< span class = "k" > end< / span >
< / pre > < / div >
< p > Some notes:< / p >
< ul >
2013-08-07 17:36:46 +02:00
< li > If you prefer not to use < code > --user< / code > and < code > --api-key< / code > above, you can fill out < code > ~/.zuliprc< / code > on your Capistrano
2013-05-29 17:55:59 +02:00
machine. For instructions on how to write that file, see < a href = "/api" > the API page< / a > .< / li >
2013-03-26 18:12:00 +01:00
< li > You may need to change the < code > deploy< / code > above to
another step of your deployment process, if you'd like the
notification to fire at a different time.< / li >
2013-03-19 21:22:50 +01:00
< / ul >
2013-06-19 23:46:11 +02:00
< em > < / em >
2013-03-19 21:22:50 +01:00
< p > < b > Congratulations! You're done!< / b > < br / > Whenever you do a
deployment, you'll get an automated notification that looks like
this:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/capistrano/001.png" / >
2013-03-19 21:22:50 +01:00
< p > < small > Thanks to Wes of TurboVote for < a href = "https://gist.github.com/cap10morgan/5100822" > submitting this integration< / a > !< / small > < / p >
< / div >
2013-10-21 21:19:31 +02:00
2016-05-09 19:59:33 +02:00
< div id = "circleci" class = "integration-instructions" >
< p > Zulip supports integration with CircleCI and can notify you of
your build statuses.< / p >
< p > First, create the stream you'd like to use for CircleCI notifications,
and subscribe all interested parties to this stream. We
recommend the name < code > circleci< / code > .< / p >
< p > < code > {{ external_api_uri }}/v1/external/circleci?api_key=abcdefgh& stream=circleci< / code > < / p >
< p > where < code > api_key< / code > is the API key of your Zulip bot,
and < code > stream< / code > is the stream name you want the
notifications sent to.< / p >
< p >
Next, modify your < code > circle.yml< / code > as described
< a href = "https://circleci.com/docs/configuration/#notify" > here< / a > .
< / p >
< p > < b > Congratulations! You're done!< / b > < br / > When a build is done,
you'll get a notification like this:< / p >
< img class = "screenshot" src = "/static/images/integrations/circleci/001.png" / >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "codebase" class = "integration-instructions" >
2013-10-01 21:38:07 +02:00
< p > First, create the streams you'd like to use for Codebase notifications. There will be two types of
messages: commit-related updates and issue-related updates. After creating these streams (we suggest naming
them < code > codebase commits< / code > and < code > codebase issues< / code > ), make sure to subscribe all interested parties.< / p >
< p > Next, download and install our < a href = "/api" > Python
bindings and example scripts< / a > on the computer you'd like to run this mirroring script from.< / p >
< p > You will need your Codebase API Username. You can find it in the settings page of your account, under
< code > API Credentials< / code > .< / p >
< p > Edit the Codebase and Zulip credentials in < code > integrations/codebase/zulip_codebase_config.py< / code > using
your favorite editor:< / p >
< div class = "codehilite" >
< pre > < span class = "n" > CODEBASE_API_USERNAME< / span > < span class = "o" > =< / span > < span class = "s" > "zulip-inc/leo-franchi-15"< / span >
< span class = "n" > CODEBASE_API_KEY< / span > < span class = "o" > =< / span > < span class = "s" > 0123456789abcdef0123456789abcdef< / span >
< span class = "n" > ZULIP_USER< / span > < span class = "o" > =< / span > < span class = "s" > "codebase-bot@example.com"< / span >
2013-12-04 21:58:45 +01:00
< span class = "n" > ZULIP_API_KEY< / span > < span class = "o" > =< / span > < span class = "s" > "0123456789abcdef0123456789abcdef"< / span >
{% if api_site_required %}< span class = "n" > ZULIP_SITE< / span > < span class = "o" > =< / span > < span class = "s" > "{{ external_api_uri }}"< / span > {% endif %}< / pre >
2013-10-01 21:38:07 +02:00
< / div >
< p > Before your first run of the script, you may optionally choose to
configure it to mirror some number of hours of prior Codebase activity:< / p >
< div class = "codehilite" >
< pre > < span class = "n" > CODEBASE_INITIAL_HISTORY_HOURS< / span > < span class = "o" > =< / span > < span class = "s" > 10< / span > < / pre >
< / div >
< p > Now, simply run the < code > api/integrations/codebase/zulip_codebase_mirror< / code > script.
If needed, this script may be restarted, and it will automatically resume from when
it was last running.< / p >
2013-08-29 20:03:59 +02:00
2013-10-01 21:38:07 +02:00
< p > < b > Congratulations! You're done!< / b > < br / > Whenever you create a new project,
commit, issue, deployment, or more, you'll get notifications in your selected streams
with the associated information.< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/codebase/001.png" / >
2013-10-01 21:38:07 +02:00
< / div >
2013-10-21 21:19:31 +02:00
2016-04-11 22:32:07 +02:00
< div id = "codeship" class = "integration-instructions" >
< p > Zulip supports integration with Codeship and can notify you of
your build statuses.< / p >
< p > First, create the stream you'd like to use for Codeship notifications,
and subscribe all interested parties to this stream. We
recommend the name < code > codeship< / code > .< / p >
< p > < code > {{ external_api_uri }}/v1/external/codeship?api_key=abcdefgh& stream=codeship< / code > < / p >
< p > where < code > api_key< / code > is the API key of your Zulip bot,
and < code > stream< / code > is the stream name you want the
notifications sent to.< / p >
< p > Next, go to your project settings - notification settings
page. The url should look like the following:< / p >
< p > < code > https://codeship.com/projects/PROJECT_ID/configure_notifications< / code > < / p >
< p > where < code > PROJECT_ID< / code > is the id of your project in Codeship.< / p >
< p > Scroll to the < code > Webhook< / code > section and fill out the form as follows:< / p >
< img class = "screenshot" src = "/static/images/integrations/codeship/001.png" / >
< p > < b > Congratulations! You're done!< / b > < br / > When a build is
triggered, you'll get a notification like this:< / p >
< img class = "screenshot" src = "/static/images/integrations/codeship/002.png" / >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "deskcom" class = "integration-instructions" >
2013-09-04 00:00:21 +02:00
< p > First, create the stream you'd like to use for Desk.com notifications,
and subscribe all interested parties to this stream. We recommend the
2013-09-05 21:23:09 +02:00
stream name < code > desk< / code > . Keep in mind you still need to
2013-09-04 00:00:21 +02:00
create the stream first even if you are using this recommendation.< / p >
< p > Next, in Desk.com, open your Admin view via the top-left corner
dropdown. In the Admin view, click on Apps, then click Install under
"Custom Action":< / p >
2013-12-17 17:37:28 +01:00
< img src = "/static/images/integrations/desk/001.png" / >
2013-09-04 00:00:21 +02:00
< p > From there, click "Install Custom Action" and accept the terms. Fill
in the form like this:< / p >
< ul >
< li > < b > Name< / b > : Zulip< / li >
< li > < b > Authentication Method< / b > : Basic Auth< / li >
2013-12-04 20:57:44 +01:00
< li > < b > URL< / b > : < code > {{ external_api_uri }}/v1/external/desk< / code > < / li >
2013-09-04 00:00:21 +02:00
< li > < b > User name< / b > : < em > your bot's user name, e.g.< / em > < code > desk-bot@yourdomain.com< / code > < / li >
< li > < b > Password< / b > : < em > your bot's API key< / em > < / li >
< / ul >
2013-12-17 17:37:28 +01:00
< img src = "/static/images/integrations/desk/002.png" / >
2013-09-04 00:00:21 +02:00
< p > From here, add a new action. You'll do this for every action you
want a notification on Zulip for:< / p >
2013-12-17 17:37:28 +01:00
< img src = "/static/images/integrations/desk/003.png" / >
2013-09-04 00:00:21 +02:00
< p > Let's say you want a notification each time a case is updated. Put
in a descriptive name like "Announce case update", and copy-paste
this to the "Appended URL path":< / p >
2016-04-21 08:48:33 +02:00
{% raw %}
2013-09-04 00:00:21 +02:00
< p > < code > ?stream=desk& topic={{case.id}}:+{{case.subject}}< / code > < / p >
2016-04-21 08:48:33 +02:00
{% endraw %}
2013-09-04 00:00:21 +02:00
< p > The "appended URL path" will be the same for every notification —
it makes sure the notification goes to the appropriate stream and topic
within Zulip. Next, copy this template Zulip message into "Message to
POST":< / p >
2016-04-21 08:48:33 +02:00
{% raw %}
2013-09-04 00:00:21 +02:00
< pre > < code
>Case [{{case.id}}, {{case.subject}}]({{case.direct_url}}), was updated.
* Status: {{case.status.name}}
* Priority: {{case.priority}}
* Customer: {{customer.name}}
* Company: {{customer.company}}
* Description: {{case.description}}< / code > < / pre >
< p > You don't need to edit that. All the funny-looking stuff inside
< code > {{< / code > and < code > }}< / code >
will be filled in by Desk.com for each event. The dialog should look
like this:< / p >
2016-04-21 08:48:33 +02:00
{% endraw %}
2013-12-17 17:37:28 +01:00
< img src = "/static/images/integrations/desk/004.png" / >
2013-09-04 00:00:21 +02:00
< p > Save it, and then click "On" next to the action to enable it. This
is important — actions are turned off by default!< / p >
< p > Now you need to create a rule that triggers this action. Desk.com's
support center has a
< a href = "https://support.desk.com/customer/portal/articles/1376" > lengthy
article on rules< / a > , but in short, click on "Cases" up at the top,
"Rules" on the left side, and then the specific event you want to notify
on — in our example, "Case Updated". Add a rule with a name like "Notify
Zulip of case update". Click on "Add Action", select "Trigger an App
Action", and select "Zulip: Announce case update". Set "Enabled" to
"Yes". The rule should look like this:< / p >
2013-12-17 17:37:28 +01:00
< img src = "/static/images/integrations/desk/005.png" / >
2013-09-04 00:00:21 +02:00
< p > Finally, click Update.< / p >
< p > < b > Congratulations! You're done!< / b > < br / > When a case is updated,
you'll see a notification like the following, to the stream
< code > desk< / code > , with a topic that matches the case's subject name:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/desk/006.png" / >
2013-09-04 00:00:21 +02:00
< / div >
2013-12-04 22:35:38 +01:00
{% if email_integration_enabled %}
2013-10-21 21:19:31 +02:00
< div id = "email" class = "integration-instructions" >
2013-08-29 20:03:59 +02:00
< p > You can send emails to Zulip! This is useful:< / p >
< ul >
< li > If you use a service that can send emails but does not easily lend
itself to more direct integration< / li >
< li > If you have an email that you want to discuss on Zulip< / li >
< li > As a structured, searchable, commentable archive for mailing list
traffic< / li >
< / ul >
< p > To send an email to a Zulip stream:< / p >
< ol >
< li > visit your < a target = "_blank" href = "../#subscriptions" > subscriptions
page< / a > and click on the stream row to expand it.< / li >
< li > Copy the stream email address
2013-12-04 22:37:49 +01:00
(e.g. < code > {{ email_gateway_example }}< / code > ). If the stream
2013-08-29 20:03:59 +02:00
name contains special characters, we've transformed the name so it is a
safe email recipient.< / li >
< li > Send an email (To, CC, and BCC all work) to the stream email
address. The email subject will become the stream topic, and the email
body will become the Zulip message content.< / li >
< / ol >
2013-09-04 18:24:49 +02:00
< p > Please note that it may take up to one minute for the message to show up
2013-08-29 20:03:59 +02:00
in Zulip.< / p >
< / div >
2013-12-04 22:35:38 +01:00
{% endif %}
2013-08-29 20:03:59 +02:00
2013-10-21 21:19:31 +02:00
2013-11-09 02:05:27 +01:00
< div id = "freshdesk" class = "integration-instructions" >
< h4 > Freshdesk< / h4 >
< p > See customer support interactions right in Zulip, with our Freshdesk
integration! Note that this integration must be set up by an administrator
for your Freshdesk instance.< / p >
< p > First, create the stream you'd like to use for Freshdesk notifications,
and subscribe all interested parties to this stream. We recommend the
stream name < code > freshdesk< / code > .< / p >
< p > Next, on your < a href = "/#settings" target = "_blank" > Zulip settings
page< / a > , create a Freshdesk bot.< / p >
< p > Now we can set up the Freshdesk events that will trigger
Zulips. Freshdesk provides separate triggering mechanisms for ticket
creation and ticket changes, so we'll set up these triggers in two
parts.< / p >
< h4 > Part 1: Zulip notifications for new Freshdesk tickets< / h4 >
< ol >
< li >
< p > Visit your Freshdesk admin page. Under the < b > "Helpdesk
Productivity"< / b > section, click the < b > "Dispatch'r"< / b > icon:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/001.png" / >
2013-11-09 02:05:27 +01:00
< p > Click the < b > "New rule"< / b > button to create a new Dispatch'r rule
that will send notifications to Zulip when Freshdesk tickets are
opened.< / p >
< / li >
< li >
< p > On the Dispatch'r rule creation page, give the rule a name and
description. Next, we need to specify the conditions under which to
trigger Zulip notifications. There isn't a shortcut for "always
generate a notification on ticket creation", so we'll instead fake it
by picking two complementary conditions: when the source < b > is
email< / b > , and when the source < b > is not email< / b > :< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/002.png" / >
2013-11-09 02:05:27 +01:00
< / li >
< li >
2013-11-12 21:59:50 +01:00
2013-11-09 02:05:27 +01:00
< p > In the < b > "Action"< / b > section, add a new action of
type < b > "Trigger Webhook"< / b > . Set the < b > "Request Type"< / b >
to < b > "POST"< / b > . Set the following < b > "Callback URL"< / b > , replacing
2013-11-12 21:59:50 +01:00
the Zulip stream with your desired stream:< / p >
2013-12-04 20:57:44 +01:00
< p > < code > {{ external_api_uri }}/v1/external/freshdesk?stream=< font color = "#00A26F" > freshdesk< / font > < / code > < / p >
2013-11-09 02:05:27 +01:00
2013-11-12 21:59:50 +01:00
< p > Check the < b > "Requires Authentication"< / b > box, and supply the bot
e-mail address and API key.< / p >
2013-11-09 02:05:27 +01:00
< p > The Action section should look like this so far:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/003.png" / >
2013-11-09 02:05:27 +01:00
< / li >
< li >
< p > Select < b > "JSON"< / b > for the < b > "Encoding"< / b > . Under the encoding, select
< b > "Advanced"< / b > . Paste the following JSON into the < b > "Content"< / b >
box:< / p >
< pre > {"freshdesk_webhook":
{
"triggered_event":"{ { triggered_event} } ",
"ticket_id":"{ { ticket.id} } ",
"ticket_url":"{ { ticket.url} } ",
"ticket_type":"{ { ticket.ticket_type} } ",
"ticket_subject":"{ { ticket.subject} } ",
"ticket_description":"{ { ticket.description} } ",
"ticket_status":"{ { ticket.status} } ",
"ticket_priority":"{ { ticket.priority} } ",
"requester_name":"{ { ticket.requester.name} } ",
"requester_email":"{ { ticket.requester.email} } ",
}
}< / pre >
< p > These ticket details are what will be forwarded to Zulip. The
pasted JSON should look like this:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/004.png" / >
2013-11-09 02:05:27 +01:00
< / li >
< li >
< p > Save your new Dispatch'r rule. The next time a Freshdesk ticket is
opened, the team will get a notification in Zulip!< / p >
< / li >
< / ol >
< p > If you only want to receive Zulip notifications on ticket creation,
stop here, you're done! If you also want notifications on important ticket
changes, please continue to the next section.< / p >
< h4 > Part 2: Zulip notifications on ticket changes< / h4 >
< ol >
< li >
< p > Visit your Freshdesk admin page. Under the < b > "Helpdesk
Productivity"< / b > section, click the < b > "Observer"< / b > icon:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/005.png" / >
2013-11-09 02:05:27 +01:00
< p > Click the < b > "New rule"< / b > button to create a new Observer rule
that will send notifications to Zulip when Freshdesk tickets are
updated.< / p >
< / li >
< li >
< p > On the Observer rule creation page, give the rule a name and
description. Under < b > "When Any Of These Events Occur"< / b > , create
these new rules:< / p >
< ul >
< li > < p > Priority is changed, from Any Priority, to Any Priority< / p > < / li >
< li > < p > Status is changed, from Any Status, to Any Status< / p > < / li >
< li > < p > Note is added, Type Any< / p > < / li >
< / ul >
< p > If you do not want to receive Zulip notifications on one or more of
these events, leave out the rule for that event.< / p >
< p > Under < b > "And The Events Are Performed By"< / b > ,
select < b > "Anyone"< / b > .< / p >
< p > So far, the rule should look like this:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/006.png" / >
2013-11-09 02:05:27 +01:00
< / li >
< li >
< p > Next, we need to specify the types of tickets that will trigger
Zulip notifications. There isn't a shortcut for "always generate a
notification on ticket update", so as before we'll instead fake it by
picking two complementary conditions: when the source < b > is email< / b > ,
and when the source < b > is not email< / b > :< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/007.png" / >
2013-11-09 02:05:27 +01:00
< / li >
< li >
< p > Under < b > "Perform These Actions"< / b > , add a new action of
type < b > "Trigger Webhook"< / b > . Set the < b > "Request Type"< / b >
to < b > "POST"< / b > . Set the following < b > "Callback URL"< / b > , replacing
2013-11-12 21:59:50 +01:00
the Zulip stream with your desired stream:< / p >
2013-12-04 20:57:44 +01:00
< p > < code > {{ external_api_uri }}/v1/external/freshdesk?stream=< font color = "#00A26F" > freshdesk< / font > < / code > < / p >
2013-11-09 02:05:27 +01:00
2013-11-12 21:59:50 +01:00
< p > Check the < b > "Requires Authentication"< / b > box, and supply the bot
e-mail address and API key.< / p >
2013-11-09 02:05:27 +01:00
< p > The Action section should look like this so far:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/008.png" / >
2013-11-09 02:05:27 +01:00
< / li >
< li >
< p > Select < b > "JSON"< / b > for the < b > "Encoding"< / b > . Under the encoding,
select < b > "Advanced"< / b > . Paste the following JSON into
the < b > "Content"< / b > box:< / p >
< pre > {"freshdesk_webhook":
{
"triggered_event":"{ { triggered_event} } ",
"ticket_id":"{ { ticket.id} } ",
"ticket_url":"{ { ticket.url} } ",
"ticket_type":"{ { ticket.ticket_type} } ",
"ticket_subject":"{ { ticket.subject} } ",
"ticket_description":"{ { ticket.description} } ",
"ticket_status":"{ { ticket.status} } ",
"ticket_priority":"{ { ticket.priority} } ",
"requester_name":"{ { ticket.requester.name} } ",
"requester_email":"{ { ticket.requester.email} } ",
}
}< / pre >
< p > These ticket details are what will be forwarded to Zulip. The
pasted JSON should look like this:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/009.png" / >
2013-11-09 02:05:27 +01:00
< / li >
< li >
< p > Save your new Observer rule. The next time a Freshdesk ticket is
updated, the team will get a notification in Zulip!< / p >
< / li >
< / ol >
< p > < b > Congratulations! You're done!< / b > < br / > You'll now see support
progress in real time in Zulip:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/freshdesk/010.png" / >
2013-11-09 02:05:27 +01:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "git" class = "integration-instructions" >
2013-02-15 23:01:55 +01:00
< p > First, download and install our < a href = "/api" > Python
bindings and example scripts< / a > on your Git server.< / p >
2013-08-26 22:58:16 +02:00
< p > Next, create the stream you'd like to use for Git notifications, and
subscribe all interested parties to this stream. The integration will use
the default stream < code > commits< / code > if no stream is supplied in the
hook; you still need to create the stream even if you are using this
default.< / p >
2013-08-07 17:55:22 +02:00
< p > Next, open < code > integrations/git/zulip_git_config.py< / code >
2013-02-15 23:01:55 +01:00
in your favorite editor, and change the following lines to
specify the email address and API key for your Git bot:< / p >
2013-08-07 18:26:11 +02:00
< div class = "codehilite" > < pre > < span class = "n" > ZULIP_USER< / span > < span class = "o" > =< / span > < span class = "s" > "git-bot@example.com"< / span >
2013-12-04 21:58:45 +01:00
< span class = "n" > ZULIP_API_KEY< / span > < span class = "o" > =< / span > < span class = "s" > "0123456789abcdef0123456789abcdef"< / span >
{% if api_site_required %}< span class = "n" > ZULIP_SITE< / span > < span class = "o" > =< / span > < span class = "s" > "{{ external_api_uri }}"< / span > {% endif %}< / pre > < / div >
2013-02-15 23:01:55 +01:00
< p > You can also specify which pushes will result in
notifications and to what stream the notifications will be sent
by modifying the < code > commit_notice_destination< / code > function
2013-08-07 17:55:22 +02:00
in < code > zulip_git_config.py< / code > . By default, pushes to
2013-02-15 23:01:55 +01:00
the < code > master< / code > and < code > test-post-receive< / code >
branches will result in a notification to
stream < code > commits< / code > .< / p >
2013-08-07 17:55:22 +02:00
< p > Save < code > integrations/git/zulip_git_config.py< / code > to
2013-02-15 23:01:55 +01:00
the < code > .git/hooks< / code > directory of your git
repository.< / p >
< p > Symlink
2013-08-07 18:32:51 +02:00
< code > /usr/local/share/zulip/integrations/git/post-receive< / code >
2013-02-15 23:01:55 +01:00
into the < code > .git/hooks< / code > directory of your git repository.< / p >
< p > < b > Congratulations! You're done!< / b > < br / > Whenever you make
a push to the < code > master< / code > branch of your git repository
2013-07-10 22:31:14 +02:00
(or whatever you configured above), the Zulip git plugin will
2013-02-15 23:01:55 +01:00
send an automated notification that looks like this:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/git/001.png" / >
2013-02-15 23:01:55 +01:00
< p > < b > Testing< / b > < br / > You can test the plugin without changing
your < code > master< / code > branch by pushing to
the < code > test-post-receive< / code > branch.< / p >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "github" class = "integration-instructions" >
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for GitHub notifications,
and subscribe all interested parties to this stream. The integration will
use the default stream < code > commits< / code > if no stream is supplied in
the hook; you still need to create the stream even if you are using this
default.< / p >
2013-12-23 16:58:25 +01:00
< p > Next, go to your repository page and click < b > "Settings"< / b > :< / p >
2014-03-05 00:54:46 +01:00
< p > < img src = "/static/images/integrations/github/001.png" / > < / p >
2013-02-06 20:25:04 +01:00
2014-03-05 00:54:46 +01:00
< p > From there, select < b > "Webhooks & Services"< / b > :< / p >
< p > < img src = "/static/images/integrations/github/002.png" / > < / p >
2013-02-06 20:25:04 +01:00
2014-03-05 00:54:46 +01:00
< p > To find the Zulip hook, you have to click on < b > Configure services< / b > .< / p >
< p > < img class = "screenshot" src = "/static/images/integrations/github/003.png" / > < / p >
< p > Select < b > "Zulip"< / b > from the list of service hooks. Fill in the API
2013-12-23 16:58:25 +01:00
key and email address for your bot and check the < b > "active"< / b >
checkbox. You can optionally supply the Zulip stream (the default
is < code > commits< / code > ) and restrict Zulip notifications to a specified
set of branches.< / p >
2014-03-05 00:54:46 +01:00
< p > Further configuration is possible. By default, commits traffic (pushes, commit comments),
Github issues traffic, and pull requests are enabled. You can exclude certain types of traffic
via the checkboxes. If you want commit traffic, issue traffic, and pull requests to go to
different places, you can use the < b > Commit Stream< / b > and < b > Issue Stream< / b > overrides;
otherwise, it is safe to leave these fields blank and just have it default to the < b > Stream< / b >
setting.< / p >
2013-12-23 16:58:25 +01:00
< p > Click the < b > "Update settings"< / b > button to complete the
2014-03-05 00:54:46 +01:00
configuration:< / p >
< p > < img src = "/static/images/integrations/github/004.png" / > < / p >
2013-02-06 20:25:04 +01:00
2013-12-23 16:58:25 +01:00
< p > < b > Congratulations! You're done!< / b > < br / > When team members push to
your repository, you'll get a Zulip notification that looks like this:< / p >
2013-12-23 15:39:50 +01:00
2014-03-05 00:54:46 +01:00
< p > < img class = "screenshot" src = "/static/images/integrations/github/005.png" / > < / p >
2013-02-06 20:25:04 +01:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "hubot" class = "integration-instructions" >
2013-10-22 16:49:48 +02:00
< ol >
2016-05-11 02:54:28 +02:00
< li > < p > Follow the "Getting Started with Hubot" section of the < a href = "https://hubot.github.com/docs/#getting-started-with-hubot" > Hubot README< / a > to create your Hubot. You'll have a new directory from which < code > bin/hubot< / code > starts a vanilla Hubot instance with the shell backend.< / p > < / li >
2013-10-22 16:49:48 +02:00
< li > In your Hubot's directory, install the Zulip adapter. Run:
< pre > < code > npm install --save hubot-zulip< / code > < / pre >
< / li >
2015-09-26 04:59:35 +02:00
< li > < p > On your < a href = "/#settings" > Zulip settings page< / a > , create a bot account. Note its username, API key and full name; you will use them on the next step.< / p > < / li >
2013-10-22 16:49:48 +02:00
< li > To run Hubot locally, use:
< pre > < code > HUBOT_ZULIP_BOT=hubot-bot@example.com HUBOT_ZULIP_API_KEY=your_key bin/hubot --adapter zulip --name "myhubot"< / code > < / pre >
< / li >
< / ol >
< p > The bot account email address and API key are passed to Hubot via environment variables < code > HUBOT_ZULIP_BOT< / code > and < code > HUBOT_ZULIP_API_KEY< / code > . The < code > --name< / code > parameter must match the name you gave the bot on the settings page.< / p >
< p >
Hubot will automatically listen for commands on all public streams. You can also invite Hubot to invite-only streams.
< / p >
< p >
To test your Hubot installation, send it an @-notification with a basic command, for example < code > @Hubot pug me< / code > , which should produce a result like this:
< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/hubot/001.png" / >
2013-10-22 16:49:48 +02:00
< p > < a href = 'https://github.com/zulip/hubot-zulip' > Source code for the hubot-zulip adapter is available on GitHub< / a > .< / p >
2016-02-23 21:04:12 +01:00
< p > < a href = "#hubot-integrations" > Check out additional Zulip integrations available via Hubot< / a > < / p >
2013-10-22 16:49:48 +02:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "jenkins" class = "integration-instructions" >
2013-02-06 22:31:26 +01:00
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for Jenkins or Hudson
notifications, and subscribe all interested parties to this stream. We
recommend the name < code > jenkins< / code > or < code > hudson< / code > .< / p >
2014-01-01 22:33:01 +01:00
< p > < strong > Install the plugin< / strong > < br / > Install the "Zulip"
plugin by going to < code > Manage Jenkins > Manage Plugins >
Available< / code > , typing in "Zulip", and clicking "Install
without restart". (For historical reasons, the plugin will be
named "Humbug Plugin")< / p >
2013-02-10 00:35:06 +01:00
2014-01-01 22:33:01 +01:00
< img class = "screenshot" src = "/static/images/integrations/jenkins/001.png" / >
2013-02-10 00:35:06 +01:00
2013-04-18 21:56:41 +02:00
< p > < strong > Configure the plugin< / strong > < br / > Once the plugin
is installed, configure it by going to < code > Manage Jenkins >
2014-01-01 22:33:01 +01:00
Configure System< / code > . Scroll to the section labeled "Zulip
2013-04-18 21:56:41 +02:00
Notification Settings", and specify your bot's email address,
2013-08-26 22:58:16 +02:00
API key, the stream receiving the notifications, and whether you'd
2013-04-18 21:56:41 +02:00
like a notification on every build, or only when the build fails
(Smart Notification).< / p >
2013-02-10 00:35:06 +01:00
2014-01-01 22:33:01 +01:00
< p > (If you don't see this option, you may first need to restart
Jenkins.)< / p >
2013-12-17 17:37:28 +01:00
< img src = "/static/images/integrations/jenkins/002.png" / >
2013-02-10 00:35:06 +01:00
2013-04-18 21:56:41 +02:00
< p > < strong > Configure a post-build action for your project< / strong > < br / >
Once you've done that, it's time to configure one of your
2013-07-10 22:31:14 +02:00
projects to use the Zulip notification plugin. From your
2013-04-18 21:56:41 +02:00
project page, click "Configure" on the left sidebar. Scroll to
the bottom until you find the section labeled "Post-build
2014-01-01 22:33:01 +01:00
Actions". Click the dropdown and select "Zulip
2013-02-10 00:35:06 +01:00
Notification". It should look as below. Then click "Save".< / p >
2013-12-17 17:37:28 +01:00
< img src = "/static/images/integrations/jenkins/003.png" / >
2013-02-10 00:35:06 +01:00
< p > < b > Congratulations! You're done!< / b > < br / > When your builds
fail or succeed, you'll see a commit message like the following
2013-12-23 15:39:50 +01:00
with a topic that matches the project name (in this case
2014-01-01 22:33:01 +01:00
"SecretProject"):< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/jenkins/004.png" / >
2013-04-05 00:15:31 +02:00
2013-04-18 21:56:41 +02:00
< p > < b > Troubleshooting< / b > < br / >
< ul >
< li > Did you set up a post-build action for your project?< / li >
< li > Does the stream you picked (e.g. < code > jenkins< / code > ) already exist? If not, add yourself to it and try again.< / li >
2013-11-18 22:57:55 +01:00
< li > Are your access key and email address correct? Test them using < a href = "/api" > our curl API< / a > .< / li >
2015-09-29 06:17:08 +02:00
< li > Still stuck? Email < a href = "mailto:zulip-devel@googlegroups.com?subject=Jenkins" > zulip-devel@googlegroups.com< / a > .< / li >
2013-06-19 23:46:11 +02:00
< / ul >
2013-11-18 22:57:55 +01:00
< / p >
2013-02-10 00:35:06 +01:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "jira" class = "integration-instructions" >
2013-08-26 22:58:16 +02:00
2013-08-28 23:48:49 +02:00
< p > < em > If you are running JIRA version 5.2 or greater, or if you are
using the hosted JIRA provided by Atlassian, you can use the built-in
web-hook support to connect to Zulip — read on. For older,
self-hosted JIRA installs, you can use our < a
href="#jira-plugin">JIRA Plugin< / a > .< / em > < / p >
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for JIRA notifications, and
subscribe all interested parties to this stream. We recommend the
name < code > jira< / code > .< / p >
2013-03-27 22:47:54 +01:00
< p > In your JIRA administration control panel, go to the Webhooks page. If you are using the OnDemand
2013-03-29 22:57:10 +01:00
hosted JIRA, follow the instructions < a href = "https://developer.atlassian.com/display/JIRADEV/JIRA+Webhooks+Overview#JIRAWebhooksOverview-WhereistheJIRAAdministrationUIforwebhooks?" >
2013-06-19 23:46:11 +02:00
on the Atlassian wiki< / a > for locating the Webhook UI.
2013-03-27 22:47:54 +01:00
< / p >
2013-04-30 23:41:46 +02:00
< p > Give your new web hook a name, and for the URL provide the following:< / p >
< p >
2013-12-04 20:57:44 +01:00
< code > {{ external_api_uri }}/v1/external/jira?api_key=abcdefgh& stream=jira< / code >
2013-03-27 22:47:54 +01:00
< / p >
2013-03-29 22:57:10 +01:00
2013-07-24 23:29:57 +02:00
< p > where < code > api_key< / code > is the API key of your Zulip bot,
and < code > stream< / code > is the stream name you want the
2013-08-26 22:58:16 +02:00
notifications sent to.< / p >
2013-04-30 23:41:46 +02:00
2013-07-10 22:31:14 +02:00
< p > Next, go back to Zulip and set up a stream called "jira," if it does not already exist.
2013-04-30 23:41:46 +02:00
(If you prefer your JIRA notifications to go to a stream other than "jira," then change the URL above to match it.)< / p >
2013-03-29 22:57:10 +01:00
< p > < b > Congratulations! You're done!< / b > < br / >
2013-07-10 22:31:14 +02:00
Updates from JIRA will be sent to the Zulip stream you specified in the JIRA web-hook.
2013-10-07 20:26:37 +02:00
< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/jira/001.png" / >
2013-03-29 22:57:10 +01:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "jira-plugin" class = "integration-instructions" >
2013-08-28 23:48:49 +02:00
< p > < em > If you are running JIRA version 5.2 or greater, or using the
hosted JIRA provided by Atlassian, we recommend using the < a
href="#jira">web-hook method< / a > above instead. This plugin
supports older versions of JIRA.< / em > < / p >
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for JIRA notifications, and
subscribe all interested parties to this stream. We recommend the
name < code > jira< / code > .< / p >
2013-03-29 22:57:10 +01:00
< h5 > Plugin mechanism< / h5 >
2013-08-26 22:58:16 +02:00
Next, download and install our < a href = "/api" > Python bindings and example scripts< / a > .
2013-03-26 17:04:12 +01:00
< p > < b > Plugin Installation< / b > < / p >
2013-03-29 22:57:10 +01:00
The JIRA integration plugin requires two JIRA plugins. Please install
2013-03-26 17:04:12 +01:00
the following plugins using the Universal Plugin Manager in your JIRA
2013-03-29 22:57:10 +01:00
installation:
2013-03-26 17:04:12 +01:00
< ul >
< li > < a href = "https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner" > Script Runner Plugin< / a > < / li >
< li > < a href = "https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.jirasslplugin" > SSL Plugin< / a > < / li >
< / ul >
< p > < b > SSL Setup< / b > < / p >
2013-07-10 22:31:14 +02:00
As Zulip is using a StartCOM SSL certificate that is not recognized by default in the Java installation shipped with JIRA,
2013-03-26 17:04:12 +01:00
you will need to tell JIRA about the certificate. Navigate to < code > Administration > System > Configure SSL< / code > and in
2013-12-04 20:57:44 +01:00
the < code > Import SSL Certificates< / code > field, enter < code > {{ external_api_uri }}< / code > . After clicking < code > Save Certificates< / code > ,
2013-03-26 17:04:12 +01:00
follow the on-screen instructions and restart JIRA for it to recognize the proper certificates.
2013-07-10 22:31:14 +02:00
< p > < b > Zulip Integration< / b > < / p >
2013-03-26 23:12:31 +01:00
Copy the folder < code > integrations/jira/org/< / code > (from the tarball you downloaded above) to your JIRA < code > classes< / code > folder.
2013-06-19 23:46:11 +02:00
For self-contained JIRA installations, this will be < code > atlassian-jira/WEB-INF/classes/< / code > , but this may be different in your deployment.
2013-08-07 18:28:46 +02:00
Edit the constants at the top of < code > org/zulip/jira/ZulipListener.groovy< / code >
2013-03-26 17:04:12 +01:00
and fill them with the appropriate values:
2013-08-07 18:28:46 +02:00
< div class = "codehilite" > < pre > < span class = "n" > String< / span > < span class = "n" > zulipEmail< / span > < span class = "o" > =< / span > < span class = "s2" > "jira-notifications-bot@example.com"< / span >
< span class = "n" > String< / span > < span class = "n" > zulipAPIKey< / span > < span class = "o" > =< / span > < span class = "s2" > "0123456789abcdef0123456789abcdef"< / span >
< span class = "n" > String< / span > < span class = "n" > zulipStream< / span > < span class = "o" > =< / span > < span class = "s2" > "JIRA"< / span >
2013-03-26 17:04:12 +01:00
< span class = "n" > String< / span > < span class = "n" > issueBaseUrl< / span > < span class = "o" > =< / span > < span class = "s2" > "https://jira.COMPANY.com/browse/"< / span >
2013-06-19 23:46:11 +02:00
< / pre > < / div >
2013-03-26 17:04:12 +01:00
< p > In the Administrators page, navigate to < code > Plugins > Other > Script Listeners< / code > . In the < code > Add Listener< / code > section, click on
2013-07-10 22:31:14 +02:00
the < code > Custom Listener< / code > option. Select the events you wish the Zulip integration to fire for, and the projects you wish Zulip to be notified for.
2013-08-07 18:28:46 +02:00
In the < code > Name of groovy class< / code > field, enter < code > org.zulip.jira.ZulipListener< / code > .
2013-11-18 22:57:55 +01:00
< / p >
2013-03-26 17:04:12 +01:00
2013-07-10 22:31:14 +02:00
< p > Click < code > Add Listener< / code > , and JIRA will now notify your Zulip of changes to your issues!< / p >
2013-03-29 22:57:10 +01:00
< p > < b > Congratulations! You're done!< / b > < br / >
Updates from JIRA will be sent to the stream you've configured, as below.< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/jira/001.png" / >
2013-03-26 17:04:12 +01:00
< / div >
2013-10-28 15:41:21 +01:00
2016-04-09 05:29:45 +02:00
< div id = "mercurial" class = "integration-instructions" >
< p > Get Zulip notifications when you < code > hg push< / code > !< / p >
< p > First, create the stream you'd like to use for Mercurial notifications,
and subscribe all interested parties to this stream. We recommend the
name < code > commits< / code > .< / p >
< p > Next, on your < a href = "/#settings" target = "_blank" > Zulip settings
page< / a > , create a Mercurial bot.< / p >
< p > Then:< / p >
< ol >
< li >
< p > Download and install our < a href = "/api" > Python bindings< / a > on the
server where the master Mercurial repository lives.< / p >
< / li >
< li >
< p > Edit the < code > hg/.hgrc< / code > configuration file for this master
Mercurial repository and add the following sections, using the
credentials for your Mercurial bot and setting the appropriate path to
the integration hook if it installs in a different location on this
system:< / p >
< pre > [hooks]
changegroup = python:/usr/local/share/zulip/integrations/hg/zulip-changegroup.py:hook
[zulip]
email = "hg-bot@example.com"
api_key = "0123456789abcdefg"
stream = "commits"
{% if api_site_required %}site = {{ external_api_uri }}{% endif %}< / pre >
< / li >
< / ol >
< p > That's all it takes for the basic setup! On the next < code > hg
push< / code > , you'll get a Zulip update for the changeset.< / p >
< h3 > More configuration options< / h3 >
< p > The Mercurial integration also supports:< / p >
< ul >
< li > linking to changelog and revision URLs for your repository's web
UI< / li >
< li > branch whitelists and blacklists< / li >
< / ul >
< h4 > Web repository links< / h4 >
< p > If you've set up your repository to
be < a href = "http://mercurial.selenic.com/wiki/QuickStart#Network_support" > browsable
via the web< / a > , add a < code > web_url< / code > configuration option to
the < code > zulip< / code > section of your master < code > .hg/hgrc< / code > to get
changelog and revision links in your Zulip notifications:< / p >
< pre > < font color = "#B6B6B4" > [zulip]
email = "hg-bot@example.com"
api_key = "0123456789abcdefg"
stream = "commits"< / font >
web_url = "http://hg.example.com:8000/"
{% if api_site_required %}site = {{ external_api_uri }}{% endif %}< / pre >
< h4 > Branch whitelists and blacklists< / h4 >
< p > By default, this integration will send Zulip notifications for
changegroup events for all branches. If you'd prefer to only receive Zulip
notifications for specified branches, add a < code > branches< / code >
configuration option to the < code > zulip< / code > section of your
master < code > .hg/hgrc< / code > , containing a comma-separated list of the
branches that should produce notifications:< / p >
< pre > < font color = "#B6B6B4" > [zulip]
email = "hg-bot@example.com"
api_key = "0123456789abcdefg"
stream = "commits"< / font >
branches = "prod,master"< / pre >
< p > You can also exclude branches that you don't want to cause
notifications. To do so, add an < code > ignore_branches< / code > configuration
option to the < code > zulip< / code > section of your
master < code > .hg/hgrc< / code > , containing a comma-separated list of the
branches that should be ignored:< / p >
< pre > < font color = "#B6B6B4" > [zulip]
email = "hg-bot@example.com"
api_key = "0123456789abcdefg"
stream = "commits"< / font >
ignore_branches = "noisy,even-more-noisy"< / pre >
< p > < b > Congratulations! You're done!< / b > < br / > When team members push new
changesets with < code > hg push< / code > , you'll get a Zulip notification that
looks like this:< / p >
< img class = "screenshot" src = "/static/images/integrations/hg/001.png" / >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "nagios" class = "integration-instructions" >
2013-10-28 15:41:21 +01:00
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for Nagios notifications,
and subscribe all interested parties to this stream. The integration will
use the default stream < code > nagios< / code > if no stream is supplied in the
configuration; you still need to create the stream even if you are using
this default.< / p >
< p > Next, download and install our < a href = "/api" > Python
2013-02-13 22:19:08 +01:00
bindings and example scripts< / a > on your Nagios server.< / p >
2013-08-07 17:36:46 +02:00
< p > Next, open < code > integrations/nagios/zuliprc.example< / code >
2013-02-13 22:19:08 +01:00
in your favorite editor, and change the following lines to
specify the email address and API key for your Nagios bot,
2013-08-07 17:36:46 +02:00
saving it to < code > /etc/nagios3/zuliprc< / code > on your Nagios
2013-02-13 22:19:08 +01:00
server:< / p >
< div class = "codehilite" > < pre > [api]
2013-12-04 22:17:23 +01:00
email = NAGIOS_BOT_EMAIL_ADDRESS
key = NAGIOS_BOT_API_KEY
{% if api_site_required %}site = {{ external_api_uri }}{% endif %}< / pre > < / div >
2013-02-13 22:19:08 +01:00
2013-08-07 18:16:52 +02:00
< p > Copy < code > integrations/nagios/zulip_nagios.cfg< / code >
2013-02-13 22:19:08 +01:00
to < code > /etc/nagios3/conf.d< / code > on your Nagios server.< / p >
2013-08-07 18:16:52 +02:00
< p > Finally, add < code > zulip< / code > to the < code > members< / code >
2013-02-13 22:19:08 +01:00
list for one or more of the contact groups in the < code > CONTACT
GROUPS< / code > section
of < code > /etc/nagios3/conf.d/contacts.cfg< / code > , doing
something like:
2013-11-18 22:57:55 +01:00
< / p >
2013-02-13 22:19:08 +01:00
< div class = "codehilite" > < pre > define contactgroup{
contactgroup_name admins
alias Nagios Administrators
2013-08-07 18:16:52 +02:00
members monitoring< span class = "na" > , zulip< / span >
2013-02-13 22:19:08 +01:00
}
< / pre > < / div >
Once you've done that, reload your Nagios configuration
2013-06-19 23:46:11 +02:00
using < code > /etc/init.d/nagios3 reload< / code > .
2013-02-13 22:19:08 +01:00
< p > < b > Congratulations! You're done!< / b > < br / > When your Nagios
system makes an alert, you'll see a message like the following,
to the stream < code > nagios< / code > (to change this, edit the
2013-08-07 18:16:52 +02:00
arguments to < code > nagios-notify-zulip< / code >
in < code > /etc/nagios3/conf.d/zulip_nagios.cfg< / code > ) with a
2013-12-23 15:39:50 +01:00
topic indicating the service with an issue:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/nagios/001.png" / >
2013-02-13 22:19:08 +01:00
< p > < b > Testing< / b > < br / > If you
have < a href = "http://nagios.sourceforge.net/docs/3_0/extcommands.html" > external
commands enabled in Nagios< / a > , you can generate a test notice
from your Nagios instance by visiting using the < code > Send
custom service notification< / code > command in
the < code > Service Commands< / code > section of any individual
service's page on your Nagios instance.< / p >
< p > < b > Troubleshooting< / b > < br / > You can confirm whether you've
2013-07-10 22:31:14 +02:00
correctly configured Nagios to run the Zulip plugin by looking
2013-08-07 18:16:52 +02:00
for < code > SERVICE NOTIFICATION< / code > lines mentioning zulip
2013-02-13 22:19:08 +01:00
in < code > /var/log/nagios3/nagios.log< / code > . You can confirm
2013-07-10 22:31:14 +02:00
whether you've configured the Zulip plugin code correctly by
2013-08-07 18:32:51 +02:00
running < code > /usr/local/share/zulip/integrations/nagios/nagios-notify-zulip< / code >
2013-02-13 22:19:08 +01:00
directly.< / p >
< / div >
2013-10-21 21:19:31 +02:00
2015-09-30 09:24:56 +02:00
2016-04-09 05:29:45 +02:00
< div id = "newrelic" class = "integration-instructions" >
< p > New Relic can send messages to a Zulip stream for alerts and
deploys.< / p >
< p > First, create the stream you'd like to use for New Relic
notifications, and subscribe all interested parties to this stream. We
recommend the name < code > newrelic< / code > .< / p >
< p > Next, in your New Relic Account Settings page, click
"Integrations", then "Alerting notifications". On the "Webhook"
tab, enter the following webhook URL:< / p >
< p > < code > {{ external_api_uri }}/v1/external/newrelic?api_key=abcdefgh& stream=newrelic< / code > < / p >
< p > where < code > api_key< / code > is the API key of your Zulip bot,
and < code > stream< / code > is the stream name you want the
notifications sent to.< / p >
< img class = "screenshot" src = "/static/images/integrations/newrelic/001.png" / >
< p > < b > Congratulations! You're done!< / b > < br / > Your New Relic events will
appear in Zulip:< / p >
< img class = "screenshot" src = "/static/images/integrations/newrelic/002.png" / >
< / div >
2015-09-30 09:24:56 +02:00
< div id = "pagerduty" class = "integration-instructions" >
< p > First, create the stream you'd like to use for Pagerduty notifications,
and subscribe all interested parties to this stream. We recommend the
stream name < code > pagerduty< / code > . Keep in mind you still need to create
the stream first even if you are using this recommendation.< / p >
< p > Next, in Pagerduty, select Services under Configuration on the top
of the page.< / p >
< img class = "screenshot" src = "/static/images/integrations/pagerduty/001.png" / >
< p > Now navigate to the service you want to integrate with Zulip. From
there, click "Add a webhook". Fill in the form like this:< / p >
< ul >
< li > < b > Name< / b > : Zulip< / li >
2016-04-21 08:48:33 +02:00
< li > < b > Endpoint URL< / b > : < code > {{ external_api_uri }}/v1/external/pagerduty?api_key=abcdefgh& stream=pagerduty< / code > < / li >
2015-09-30 09:24:56 +02:00
< / ul >
< img class = "screenshot" src = "/static/images/integrations/pagerduty/002.png" / >
< / div >
2013-12-05 22:31:37 +01:00
< div id = "perforce" class = "integration-instructions" >
< p > Zulip supports integration with Perforce as a
< a href = "http://www.perforce.com/perforce/doc.current/manuals/p4sag/chapter.scripting.html" > trigger< / a >
that fires once a changelist is submitted and committed. To do this:< / p >
< ol >
< li > Download and install our < a href = "/api" > Python bindings< / a > on the
server that hosts your Perforce depot. The Perforce trigger will be
installed to a location like
< code > /usr/local/share/zulip/integrations/perforce< / code > < / li >
< li > Open < code > integrations/perforce/zulip_perforce_config.py< / code > in
your favorite editor and change the < code > ZULIP_USER< / code > and
< code > ZULIP_API_KEY< / code > variables at the top of the file to the
credentials for the bot you'd like to use for this integration.< / li >
< li > Edit your
< a href = "http://www.perforce.com/perforce/doc.current/manuals/p4sag/chapter.scripting.html#d0e14583" > trigger table< / a >
with < code > p4 triggers< / code > and add an entry something like the
following:
< pre > notify_zulip change-commit //depot/... "python /usr/local/share/zulip/integrations/perforce/zulip_change-commit.py %change% %changeroot%"< / pre >
< / li >
< li > By default, this hook will send to streams of the form
< code > depot_subdirectory-commits< / code > . So, a changelist that modifies
files in < code > //depot/foo/bar/baz< / code > will result in a message to
stream < code > foo-commits< / code > . Messages about changelists that modify
files in the depot root or files in multiple direct subdirectories of
the depot root will be sent to < code > depot-commits< / code > . If you'd
prefer different behavior, such as all commits across your depot going
to one stream, change it now in < code > zulip_perforce_config.py< / code > .
Make sure that everyone interested in getting these post-commit Zulips
is subscribed to the relevant streams!< / li >
< / ol >
< p > < b > Congratulations! You're done!< / b > < br / > When you commit to your
Perforce depot the team can see updates in real time in
Zulip:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/perforce/001.png" / >
2013-12-05 22:31:37 +01:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "phabricator" class = "integration-instructions" >
2013-09-23 23:18:17 +02:00
2016-03-14 22:12:46 +01:00
< p > Zulip supports integration with Phabricator and can notify you of the
2013-09-23 23:18:17 +02:00
latest items in your Phabricator feed.< / p >
< p > You can follow the instructions at
< a href = "https://github.com/zulip/phabricator-to-zulip" >
https://github.com/zulip/phabricator-to-zulip
< / a >
to get it set up.
2013-11-18 22:57:55 +01:00
< / p >
2013-09-23 23:18:17 +02:00
< / div >
2016-03-14 22:12:46 +01:00
< div id = "pingdom" class = "integration-instructions" >
< p > Zulip supports integration with Pingdom and can notify you of
uptime status changes from your Pingdom dashboard.< / p >
< p > First, create the stream you'd like to use for Pingdom notifications,
and subscribe all interested parties to this stream. We
recommend the name < code > pingdom< / code > .< / p >
< p > < code > {{ external_api_uri }}/v1/external/pingdom?api_key=abcdefgh& stream=pingdom< / code > < / p >
< p > where < code > api_key< / code > is the API key of your Zulip bot,
and < code > stream< / code > is the stream name you want the
notifications sent to.< / p >
< p > Next, under following url: < / p >
< p > < code > https://my.pingdom.com/reports/integration/settings< / code > < / p >
< p > create your integration by clicking on < code > Add Integration< / code > button and filling form as following:< / p >
< img class = "screenshot" src = "/static/images/integrations/pingdom/001.png" / >
< p > Last, during creating or editing your check, scroll down to < code > Connect Integrations< / code >
section and ensure your integration is checked< / p >
< p > < b > Congratulations! You're done!< / b > < br / > Example Zulip notification
looks like this:< / p >
< img class = "screenshot" src = "/static/images/integrations/pingdom/002.png" / >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "pivotal" class = "integration-instructions" >
2013-04-18 17:53:45 +02:00
2016-03-14 22:12:46 +01:00
< p > Zulip supports integration with Pivotal Tracker and can notify you of changes
2013-08-26 22:58:16 +02:00
to the stories in your Pivotal Tracker project.< / p >
< p > First, create the stream you'd like to use for Pivotal Tracker
notifications, and subscribe all interested parties to this stream. We
recommend the name < code > pivotal< / code > .< / p >
< p > Next, in the Settings page for your project, choose the Integrations
tab. Scroll down to the < code > Activity Web Hook< / code > section, and enter
the following url:< / p >
2013-12-04 20:57:44 +01:00
< p > < code > {{ external_api_uri }}/v1/external/pivotal?api_key=abcdefgh& stream=pivotal< / code > < / p >
2013-04-18 17:53:45 +02:00
2013-07-24 23:29:57 +02:00
< p > where < code > api_key< / code > is the API key of your Zulip bot,
and < code > stream< / code > is the stream name you want the
2013-08-26 22:58:16 +02:00
notifications sent to.< / p >
2013-02-13 22:19:08 +01:00
2014-01-09 17:11:50 +01:00
< p > Choose version 5 of the API. Zulip supports both version 3 and version 5, but
version 5 contains more information that lets Zulip format more useful messages.< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/pivotal/001.png" / >
2013-04-18 17:53:45 +02:00
2013-10-07 20:26:37 +02:00
< p > < b > Congratulations! You're done!< / b > < br / > When you make changes in Pivotal Tracker they will be reflected in Zulip:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/pivotal/002.png" / >
2013-04-18 17:53:45 +02:00
< / div >
2013-10-21 21:19:31 +02:00
2013-12-24 04:46:59 +01:00
< div id = "puppet" class = "integration-instructions" >
< p > Zulip supports Puppet integration and can notify you when Puppet runs fail (or when they happen at all).< / p >
< p > You can follow the instructions at
< a href = "https://forge.puppetlabs.com/mbarr/puppet_zulip" >
https://forge.puppetlabs.com/mbarr/puppet_zulip
< / a >
to get it set up.
< / p >
< p > < small > Thanks to Matt from Kensho for submitting this integration!< / small > < / p >
2013-08-26 22:58:16 +02:00
2013-07-23 21:50:29 +02:00
< / div >
2013-10-21 21:19:31 +02:00
< div id = "redmine" class = "integration-instructions" >
2013-09-27 23:44:25 +02:00
< p > Get information on new or updated Redmine issues right in
Zulip with our Zulip Redmine plugin! Note: this setup must be
done by a Redmine Administrator.< / p >
< p > First, create the stream you'd like to use for Redmine notifications,
and subscribe all interested parties to this stream. We recommend the
name < code > redmine< / code > .< / p >
< p > Then:< / p >
< ol >
< li >
< p > Clone
the < a href = "https://github.com/zulip/zulip-redmine-plugin" > Zulip
Redmine plugin repository< / a > by running:< / p >
< pre > git clone https://github.com/zulip/zulip-redmine-plugin< / pre >
< / li >
< li >
< p > Follow
the < a href = "http://www.redmine.org/projects/redmine/wiki/Plugins" > Redmine
plugin installation guide< / a > to install
the < code > zulip_redmine< / code > plugin directory, which is a
subdirectory of the < code > zulip-redmine-plugin< / code > repository
directory. In a nutshell, the steps are:< / p >
< ol type = "A" >
< li >
< p > Copy the < code > zulip_redmine< / code > directory to
the < code > plugins< / code > directory of your Redmine
instance.< / p > < / li >
< li >
< p > Update the Redmine database by running (for Rake 2.X, see the
guide for instructions for older versions):< / p >
< pre > rake redmine:plugins:migrate RAILS_ENV=production< / pre >
< / li >
< li >
< p > Restart your Redmine instance.< / p >
< / li >
< / ol >
< p > The Zulip plugin is now registered with Redmine!< / p >
< / li >
< li >
< p > On your < a href = "/#settings" target = "_blank" > Zulip settings
page< / a > , create a new Redmine bot.< / p >
< / li >
< li >
< p > To configure Zulip notification settings that apply to many
projects in one go, in Redmine click the "Administration" link in
the top left. Click the "Plugins" link on the Administration page,
and click the "Configure" link to the right of the Zulip plugin
description. In the "Projects" section, select all projects to which
you want these settings to apply.< / p >
< p > To configure Zulip notifications for a particular Redmine project,
visit the project's Settings page.< / p >
< p >
In either case, fill out the bot email address and API key, and the
Zulip stream that should receive notifications. Apply your changes.
< / p >
< / li >
< li >
< p > To test the plugin, create an issue or update an existing issue in
a Redmine project that has Zulip notifications configured (any
project, if you've configured global settings).< / p >
< / li >
< / ol >
< p > < b > Congratulations! You're done!< / b > < br / > When you update issues in
Redmine, the team can see these updates in real time in Zulip:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/redmine/001.png" / >
2013-09-27 23:44:25 +02:00
< / div >
2013-10-21 21:19:31 +02:00
2014-01-02 19:02:17 +01:00
< div id = "rss" class = "integration-instructions" >
< h4 > RSS< / h4 >
< p > Get service alerts, news, and new blog posts right in Zulip with our
RSS integration!< / p >
< p > First, create the stream you'd like to use for RSS notifications, and
subscribe all interested parties to this stream. We recommend the
name < code > rss< / code > .< / p >
< p > Next, on your < a href = "/#settings" target = "_blank" > Zulip settings
page< / a > , create an RSS bot.< / p >
< p > Then, download and install our < a href = "/api" > Python bindings< / a > on
the server where the RSS bot will live. The RSS integration will be
installed to a location
like < code > /usr/local/share/zulip/integrations/rss/rss-bot< / code > .< / p >
< p > Follow the instructions in the < code > rss-bot< / code > script for
configuring the bot, adding your subscriptions, and setting up a cron job
to run the bot.< / p >
< p > < b > Congratulations! You're done!< / b > < br / > When new items appear in
your feeds, the team can see these updates in real time in Zulip:< / p >
< img class = "screenshot" src = "/static/images/integrations/rss/001.png" / >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "stash" class = "integration-instructions" >
< h4 > Stash< / h4 >
< p > See what the team is committing to Stash right in Zulip with the Zulip
Stash plugin!< / p >
< p > First, create the stream you'd like to use for Stash notifications, and
subscribe all interested parties to this stream. We recommend the
name < code > commits< / code > .< / p >
< p > Next, on your < a href = "/#settings" target = "_blank" > Zulip settings
page< / a > , create a Stash bot.< / p >
< p > Then:< / p >
< ol >
< li >
< p > Visit the Settings page for the Project that you'd like to generate
Zulip notifications. Click the "Hooks" option in the left sidebar, and
click "Add Hook" on the resulting page. Click the "Search for hook
plugins" link:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/stash/001.png" / >
2013-10-21 21:19:31 +02:00
< / li >
< li >
< p > On the search results page, look for and install the "Post-Receive
WebHook for Stash" plugin:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/stash/002.png" / >
2013-10-21 21:19:31 +02:00
< / li >
< li >
< p > Return to the Settings page for this Project and click the "Hooks"
option in the left sidebar. The newly-installed post-receive webhook
plugin is now listed in the "Post-receive" hooks section. Click the
edit icon next to the hook to configure it:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/stash/003.png" / >
2013-10-21 21:19:31 +02:00
< / li >
< li >
< p > Supply the following webhook URL, replacing the bot email address,
bot API key, and Zulip stream with the appropriate
information. < b > Note:< / b > the < code > @< / code > -sign in the bot e-mail
address must be escaped to < code > %40< / code > :< / p >
2013-12-04 20:57:44 +01:00
< p > < code > {{ external_uri_scheme }}< font color = "#00A26F" > stash-bot%40example.com< / font > :< font color = "#00A26F" > api_key< / font > @{{ external_api_path }}/v1/external/stash?stream=< font color = "#00A26F" > commits< / font > < / code > < / p >
2013-10-21 21:19:31 +02:00
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/stash/004.png" / >
2013-10-21 21:19:31 +02:00
< / li >
< / ol >
< p > < b > Congratulations! You're done!< / b > < br / > When you push to Stash, the
team can see these updates in real time in Zulip:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/stash/005.png" / >
2013-10-21 21:19:31 +02:00
< / div >
< div id = "subversion" class = "integration-instructions" >
2013-05-29 16:38:46 +02:00
2013-07-10 22:31:14 +02:00
< p > It is easy to send Zulips on SVN commits, by configuring a post-commit
2013-05-29 16:38:46 +02:00
hook. To do this:< / p >
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for SVN commit
notifications, and subscribe all interested parties to this stream. The
integration will use the default stream < code > commits< / code > if no stream
is supplied in the hook; you still need to create the stream even if you
are using this default.< / p >
< p > Then:< / p >
2013-05-29 16:38:46 +02:00
< ol >
< li > Download and install our < a href = "/api" > Python bindings< / a > on the
server where the SVN repository lives.< / li >
< li > Install < code > pysvn< / code > . On Linux, you can install
the < code > python-svn< / code > package. On other platforms, you can install
a binary or from source following
the < a href = "http://pysvn.tigris.org/project_downloads.html" > instructions
on the pysvn website< / a > .< / li >
2013-08-07 17:55:22 +02:00
< li > Copy < code > integrations/svn/zulip_svn_config.py< / code >
2013-05-29 16:38:46 +02:00
and < code > integrations/svn/post-commit< / code > from the API bindings
directory to the < code > hooks< / code > subdirectory of your SVN
repository.< / li >
2013-12-04 22:01:10 +01:00
< li > < p > Next, open < code > integrations/git/zulip_svn_config.py< / code >
in your favorite editor, and change the following lines to
configure your SVN integration:< / p >
< div class = "codehilite" > < pre > < span class = "n" > ZULIP_USER< / span > < span class = "o" > =< / span > < span class = "s" > "svn-bot@example.com"< / span >
< span class = "n" > ZULIP_API_KEY< / span > < span class = "o" > =< / span > < span class = "s" > "0123456789abcdef0123456789abcdef"< / span >
{% if api_site_required %}< span class = "n" > ZULIP_SITE< / span > < span class = "o" > =< / span > < span class = "s" > "{{ external_api_uri }}"< / span > {% endif %}< / pre > < / div >
< / li >
2013-05-29 16:38:46 +02:00
< li > The default stream used by this post-commit hook
is < code > commits< / code > ; if you'd prefer a different stream, change it
2013-08-07 17:55:22 +02:00
now in < code > zulip_svn_config.py< / code > . Make sure that everyone
2013-07-10 22:31:14 +02:00
interested in getting these post-commit Zulips is subscribed to that
2013-05-29 16:38:46 +02:00
stream!< / li >
< / ol >
< p > < b > Congratulations! You're done!< / b > < br / > When you commit to this SVN
2013-07-10 22:31:14 +02:00
repository, the team can see these updates in real time in Zulip:< / p >
2013-05-29 16:38:46 +02:00
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/svn/001.png" / >
2013-05-29 16:38:46 +02:00
< / div >
2013-10-21 21:19:31 +02:00
2016-04-28 15:46:00 +02:00
< div id = "taiga" class = "integration-instructions" >
< p > Go on your < a href = "/#settings" > Zulip settings page< / a > , create a Taiga bot.
Please note the bot name and API key.< / p >
< p > Since Taiga allows you to integrate services on a per
project basis, you have to perform the following steps
for < b > every project< / b > that you want to send
notifications to Zulip.< / p >
< ol >
< li >
< p > Go to Admin < b > >< / b > Integration < b > >< / b > Webhooks menu.< / p >
< / li >
< li >
< p > Click < b > Add a new webhook< / b > .< / p >
< / li >
< li >
< p > Fill out the form by following the instructions:
< ul >
< li >
< b > Name< / b > - to recognize this service, preferably < code > Zulip< / code >
< / li >
< li >
< b > URL< / b > -
< pre >
{{ external_api_uri }}/v1/external/taiga?stream=STREAM_NAME& topic=TOPIC_NAME& api_key=BOT_API_KEY< / pre >
< ul >
< li > < code > STREAM_NAME< / code > - The url-encoded name of
stream which you want to receive notifications.
You can use an existing Zulip stream or create a
new one for this.
< / li >
< li > < code > TOPIC_NAME< / code > - The url-encoded
topic where your Taiga notifications will be
posted. (Read the notes below.)< / li >
< li > < code > BOT_API_KEY< / code > - API key created in Zulip.< / li >
< / ul >
< p > Remember to url-encode the stream and topic
names. E.g. spaces need to be replaced
with < code > %20< / code > (e.g. so if you want your stream
to be called "My awesome project", STREAM_NAME
should be < code > My%20awesome%20project< / code > ).< / p >
< / li >
< li >
< b > Secret key< / b > - once again the API key created in Zulip.
< / li >
< / ul >
< / p >
< / li >
< li >
< p > Click < b > Save< / b > once you've finished filling out the form.< / p >
< / li >
< / ol >
< p > That's it! Your actions on Taiga should now cause
notifications on the Zulip stream you specified above.
< img class = "screenshot"
src="/static/images/integrations/taiga/001.png" /> < hr / >
There are < b > two different ways< / b > you may want to consider
when organizing your Taiga - Zulip integration:< / p >
< ul >
< li >
Use special Zulip stream for Taiga messages - name
it < code > Taiga< / code > . (Make sure to create this stream
first!) For every integrated project, provide a new topic.
< pre >
STREAM_NAME = Taiga
TOPIC = Project< / pre >
< / li >
< li >
If you already have a Zulip stream for managing a project,
you can also use this existing stream and add Taiga
notifications using special topic.(Remember about
substituting spaces with < code > %20< / code > ).< pre >
STREAM_NAME = My%20existing%20Zulip%20stream
TOPIC = Taiga< / pre >
< / li >
< / ul >
< / div >
2016-04-21 19:18:41 +02:00
< div id = "teamcity" class = "integration-instructions" >
< p > See your Teamcity build status in Zulip!< / p >
< p > First, create the stream you'd like to use for Teamcity
notifications, and subscribe all interested parties to this stream. We
recommend the name < code > teamcity< / code > .< / p >
< p > Next, set up a bot for the integration. You'll need the bot's API key
to construct a URL for Teamcity.< / p >
< p > Next, install the < a href = "https://github.com/tcplugins/tcWebHooks/releases" > tcWebHooks plugin< / a >
onto your Teamcity server. Follow the plugin instructions in your
Teamcity documentation, or refer to
< a href = "https://confluence.jetbrains.com/display/TCD9/Installing+Additional+Plugins" > the online Teamcity documentation< / a > .< / p >
< p > Next, in your Teamcity project overview page,
click the "Webhooks" tab, and add a new project webhook.
Enter the following URL:< / p >
< p > < code > {{ external_api_uri }}/v1/external/teamcity?api_key=abcdefgh& stream=teamcity< / code > < / p >
< p > where < code > api_key< / code > is the API key of your Zulip bot,
and < code > stream< / code > is the stream name you want the
notifications sent to.< / p >
< p > Uncheck all "Trigger on Events" options, and check
"Trigger when build is Successful" and "Trigger when build Fails".
Optionally, check "Only trigger when build changes from Failure to Success"
and "Only trigger when build changes from Success to Failure".< / p >
< p > Set the Payload Format to "JSON" and save your webhook.< / p >
< img class = "screenshot" src = "/static/images/integrations/teamcity/001.png" / >
< p > < b > Congratulations! You're done!< / b > < br / > Your Teamcity build
notifications will appear in Zulip:< / p >
< img class = "screenshot" src = "/static/images/integrations/teamcity/002.png" / >
< p > < b > Personal Builds< / b > < br / > When a user runs a personal build, if Zulip can
map their Teamcity username to a Zulip user, that Zulip user will receive a
private message with the result of their personal build.< / p >
< img class = "screenshot" src = "/static/images/integrations/teamcity/003.png" / >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "trac" class = "integration-instructions" >
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for Trac notifications, and
subscribe all interested parties to this stream. The integration will use
the default stream < code > trac< / code > if no stream is supplied in the
hook; you still need to create the stream even if you are using this
default.< / p >
< p > Next, download and install our < a href = "/api" > Python
2013-02-14 19:46:23 +01:00
bindings and example scripts< / a > on your Trac server.< / p >
2013-02-06 22:31:26 +01:00
2013-08-07 17:55:22 +02:00
< p > Next, open < code > integrations/trac/zulip_trac_config.py< / code > in
2013-02-13 22:48:16 +01:00
your favorite editor, and change the following lines to specify
your bot's email address, API key, and where you'd like your
2013-02-06 22:31:26 +01:00
notification messages to go (by default,
stream < code > trac< / code > ):< / p >
2013-08-07 18:01:49 +02:00
< div class = "codehilite" > < pre > < span class = "n" > ZULIP_USER< / span > < span class = "o" > =< / span > < span class = "s" > "trac-notifications-bot@example.com"< / span >
< span class = "n" > ZULIP_API_KEY< / span > < span class = "o" > =< / span > < span class = "s" > "0123456789abcdef0123456789abcdef"< / span >
2013-02-06 22:31:26 +01:00
< span class = "n" > STREAM_FOR_NOTIFICATIONS< / span > < span class = "o" > =< / span > < span class = "s" > "trac"< / span >
2013-12-04 21:58:45 +01:00
< span class = "n" > TRAC_BASE_TICKET_URL< / span > < span class = "o" > =< / span > < span class = "s" > "https://trac.example.com/ticket"< / span >
{% if api_site_required %}< span class = "n" > ZULIP_SITE< / span > < span class = "o" > =< / span > < span class = "s" > "{{ external_api_uri }}"< / span > {% endif %}< / pre > < / div >
2013-02-06 22:31:26 +01:00
2013-08-07 18:01:49 +02:00
< p > Copy < code > integrations/trac/zulip_trac.py< / code >
2013-08-07 17:55:22 +02:00
and < code > integrations/trac/zulip_trac_config.py< / code > into
2013-02-14 19:46:23 +01:00
your Trac installation's < code > plugins/< / code >
subdirectory. Once you've done that, edit your Trac
installation's < code > conf/trac.ini< / code > to
2013-08-07 18:01:49 +02:00
add < code > zulip_trac< / code > to the < code > [components]< / code >
2013-02-14 19:46:23 +01:00
section, as follows:< / p >
2013-02-06 22:31:26 +01:00
< div class = "codehilite" > < pre > < span class = "k" > [components]< / span >
2013-08-07 18:01:49 +02:00
< span class = "na" > zulip_trac< / span > < span class = "o" > =< / span > < span class = "s" > enabled< / span > < / pre > < / div >
2013-02-06 22:31:26 +01:00
< p > You may then need to restart Trac (or Apache) so that Trac will load our plugin.< / p >
< p > < b > Congratulations! You're done!< / b > < br / > When people open
new tickets (or edit existing tickets), you'll see a message
like the following, to the stream < code > trac< / code > (or whatever
2013-12-23 15:39:50 +01:00
you configured above) with a topic that matches the ticket
2013-02-06 22:31:26 +01:00
name:< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/trac/001.png" / >
2013-02-06 22:31:26 +01:00
2013-02-13 22:48:16 +01:00
< p > < b > Additional trac configuration< / b > < br / > After using the plugin
for a while, you may want to customize which changes to tickets
2013-07-10 22:31:14 +02:00
result in a Zulip notification using
2013-02-13 22:48:16 +01:00
the < code > TRAC_NOTIFY_FIELDS< / code > setting
2013-08-07 17:55:22 +02:00
in < code > zulip_trac_config.py< / code > .< / p >
2013-02-06 22:31:26 +01:00
< / div >
2013-10-21 21:19:31 +02:00
2016-04-09 05:29:45 +02:00
< div id = "travis" class = "integration-instructions" >
< p > See your Travis CI build notifications in Zulip!< / p >
< p > First, create the stream you'd like to use for notifications, and subscribe
all interested parties to this stream. We recommend the name < code > travis< / code > .< / p >
< p > Next, set up a bot for the integration. You'll need the bot's API key
to construct a URL for Travis CI.< / p >
< p > Finally, set up a webhook in your < code > .travis.yml< / code > file:< / p >
< pre >
notifications:
webhooks:
- https://zulip.example.com/api/v1/external/travis?stream=travis& topic=build-status& api_key=abcdefgh
< / pre >
< p > < b > Congratulations! You're done!< / b > < br / > When a code build occurs,
you're receive a notification on the specified stream and topic.< / p >
< img class = "screenshot" src = "/static/images/integrations/travis/001.png" / >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "trello" class = "integration-instructions" >
2013-08-26 22:58:16 +02:00
< p > First, create the stream you'd like to use for Trello notifications,
and subscribe all interested parties to this stream. We recommend the
name < code > trello< / code > .< / p >
< p > Next, download a copy
2016-01-20 19:11:53 +01:00
of < a href = "https://github.com/zulip/trello-to-zulip" > trello-to-zulip< / a >
2013-07-23 17:21:25 +02:00
and follow the instructions in < code > README.md< / code > . When you
make changes in Trello, they will be reflected in Zulip:
< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/trello/001.png" / >
2013-07-23 17:21:25 +02:00
< p > < small > Thanks to Nathan from FoundationDB for < a href = "https://github.com/nathanlws/trello-to-zulip" > submitting this integration< / a > !< / small > < / p >
< / div >
2013-10-21 21:19:31 +02:00
< div id = "twitter" class = "integration-instructions" >
2013-10-16 04:28:13 +02:00
< p > See Twitter search results in Zulip! This is great for seeing and
discussing who is talking about you, friends, competitors, or important
topics in real time.< / p >
< p > First, create the stream you'd like to use for tweets, and subscribe
all interested parties to this stream. We recommend the
name < code > twitter< / code > .< / p >
< p > Next, download and install our < a href = "/api" > Python bindings and
example scripts< / a > . This bot should be set up on a trusted machine,
because your API key is visible to local users through the command line or
config file.< / p >
< p > Next, install < b > version 1.0 or later< / b > of
the < code > twitter-python< / code > library. If your operating system
distribution doesn't package a new enough version, you can install the
library from source
from < a href = "https://github.com/bear/python-twitter" > the GitHub
repository< / a > .< / p >
< p > Next, set up Twitter authentication. This bot uses OAuth to
authenticate with Twitter, and in order to obtain a consumer key & secret,
you must register a new application under your Twitter account:< / p >
< ol >
< li >
Log in to < a href = "http://dev.twitter.com" > http://dev.twitter.com< / a > .
< / li >
< li >
In the menu under your username,
click < a href = "https://dev.twitter.com/apps" > My Applications< / a > . From
this page, create a new application.
< / li >
< li >
Click on the application you created and click "create my access
token". Fill in the requested values.
< / li >
< / ol >
< p > To configure and deploy this bot:< / p >
< ol >
< li >
Create a < code > ~/.zulip_twitterrc< / code > with the following
contents:
< pre > [twitter]
consumer_key =
consumer_secret =
access_token_key =
access_token_secret =< / pre >
< / li >
< li >
Test the script by running it manually:
< pre > /usr/local/share/zulip/integrations/twitter/twitter-search-bot --search="@nprnews,quantum physics"< / pre >
Note: < code > twitter-search-bot< / code > may install to a different
location on your operating system distribution.
< / li >
< li >
Configure a crontab entry for this script. A sample crontab entry that
will process tweets every minute is:
< pre > * * * * * /usr/local/share/zulip/integrations/twitter/twitter-search-bot --search="@nprnews,quantum physics"< / pre >
< / li >
< / ol >
< p > < b > Congratulations! You're done!< / b > < br / > When someone tweets a
message containing one of your search terms, you'll get a Zulip on your
specified stream, with the search term as the topic.< / p >
2013-12-17 17:37:28 +01:00
< img class = "screenshot" src = "/static/images/integrations/twitter/001.png" / >
2016-01-10 08:23:01 +01:00
< p > Note that the twitter search bot integration < b > just sends
links to tweets< / b > ; the pretty inline previews of tweets are
generated by the Twitter card rendering integration configured
in < code > /etc/zulip/settings.py< / code > on the Zulip server.< / p >
2013-10-16 04:28:13 +02:00
< / div >
2014-01-13 19:25:57 +01:00
2016-03-25 17:19:18 +01:00
< div id = "yo-app" class = "integration-instructions" >
< p > See your Yo App notifications in Zulip!< / p >
2016-05-11 04:12:05 +02:00
< p > < a href = "/api/#api_keys" > Go to your Zulip settings and set up a Zulip bot for the
integration.< / a > You'll need the bot's API key to construct a URL for
< a href = "http://docs.justyo.co/docs/receiving-a-yo-with-the-api" > Yo App Callback< / a > .< / p >
2016-03-25 17:19:18 +01:00
< p > You will receive your notifications as a private message between you and the bot.< / p >
2016-05-11 04:12:05 +02:00
< p > Create a URL using your bot's API key and the email address associated with your Zulip account:< / p >
< p > < pre > < code >
https://zulip.example.com/api/v1/external/yo?email=awesome@zulip.example.com& api_key=abcdefgh
< / code > < / pre > < / p >
2016-03-25 17:19:18 +01:00
2016-05-11 04:12:05 +02:00
< p > Copy the URL created and go to < a href = "https://yoapi.justyo.co" > yoapi.justyo.co< / a > .< / p >
< p > Sign in using your username and password and go to < b > Edit Profile< / b > .< / p >
2016-03-25 17:19:18 +01:00
< img class = "screenshot" src = "/static/images/integrations/yo-app/001.png" / >
2016-05-11 04:12:05 +02:00
< p > Paste the URL in the < b > Callback< / b > field and click on < b > Update< / b > .< / p >
2016-03-25 17:19:18 +01:00
< p > < b > Congratulations! You're done!< / b > < br / > When someone sends your username a Yo,
you'll receive a notification as a private message from the bot
like this:< / p >
< img class = "screenshot" src = "/static/images/integrations/yo-app/002.png" / >
< p > Multiple users can use the same Yo bot; each user should use
their own Zulip account email in the webhook URL.< / p >
< / div >
2014-01-13 19:25:57 +01:00
< div id = "zendesk" class = "integration-instructions" >
< p > First, create the stream you'd like to use for Zendesk notifications,
and subscribe all interested parties to this stream. We recommend the
stream name < code > zendesk< / code > . Keep in mind you still need to create
the stream first even if you are using this recommendation.< / p >
< p > Next, in Zendesk, open your Admin view via gear in the bottom-left
corner. In the Admin view, click on Extensions, then click "add
target".< / p >
< img class = "screenshot" src = "/static/images/integrations/zendesk/001.png" / >
< img class = "screenshot" src = "/static/images/integrations/zendesk/002.png" / >
< p > From there, click "URL target". Fill in the form like this:< / p >
< ul >
< li > < b > Title< / b > : Zulip< / li >
2016-04-21 08:48:33 +02:00
< li > < b > URL< / b > : < code > {{ external_api_uri }}{% raw %}/v1/external/zendesk?ticket_title={{ticket.title}}& ticket_id={{ticket.id}}& stream=zendesk{% endraw %}< / code > < / li >
2014-01-13 19:25:57 +01:00
< li > < b > Method< / b > : POST< / li >
< li > < b > Attribute Name< / b > : message< / li >
< li > < b > Username< / b > : < em > your bot's user name, e.g.< / em > < code > zendesk-bot@yourdomain.com< / code > < / li >
< li > < b > Password< / b > : < em > your bot's API key< / em > < / li >
< / ul >
< img class = "screenshot" src = "/static/images/integrations/zendesk/003.png" / >
< p > Now select "Test Target" and click Submit. A test message should
appear in the zendesk stream. If the message was received, save the
target by selecting "Create target" and clicking Submit.< / p >
< p > From here, add a new trigger. You'll do this for every action you want
to create a Zulip notification. Triggers are added by selecting Triggers
in the left menu and then clicking "add trigger" in the top right.< / p >
< img class = "screenshot" src = "/static/images/integrations/zendesk/004.png" / >
< img class = "screenshot" src = "/static/images/integrations/zendesk/005.png" / >
< p > Let's say you want a notification each time a ticket is updated. Put
in a descriptive title like "Announce ticket update". Under "Meet all of
the folllowing conditions" select "Ticket: is..." and then select
Updated. In the "Perform these actions" section select "Notification:
Notify target" then select Zulip.< / p >
< p > Next we need need to enter the message body into Message. You can use
Zulip markdown and the Zendesk placeholders when creating your message.
You can copy this example template:< / p >
2016-04-21 08:48:33 +02:00
{% raw %}
2014-01-13 19:25:57 +01:00
< pre > < code > Ticket [#{{ticket.id}}: {{ticket.title}}]({{ticket.link}}), was updated by {{current_user.name}}
* Status: {{ticket.status}}
* Priority: {{ticket.priority}}
* Type: {{ticket.ticket_type}}
2014-01-14 19:01:37 +01:00
* Assignee: {{ticket.assignee.name}}
2014-01-13 19:25:57 +01:00
* Tags: {{ticket.tags}}
* Description:
``` quote
{{ticket.description}}
``` < / code > < / pre >
2016-04-21 08:48:33 +02:00
{% endraw %}
2014-01-13 19:25:57 +01:00
< img src = "/static/images/integrations/zendesk/006.png" / >
< p > Finally, click Submit.< / p >
< p > < b > Congratulations! You're Done!< / b > < br / > When a ticket is updated
you will see a notification like the following, to the stream
< code > zendesk< / code > , with a topic that matches the ticket's subject
name:< / p >
< img class = "screenshot" src = "/static/images/integrations/zendesk/007.png" / >
< / div >
2013-10-21 21:19:31 +02:00
< / div >
2013-02-06 20:25:04 +01:00
2013-04-02 20:01:23 +02:00
{% endblock %}
{% block customhead %}
2016-04-21 08:48:33 +02:00
{{ super() }}
2013-02-06 20:25:04 +01:00
< script type = "text/javascript" >
$(function() {
$("a.title").addClass("show-integral");
2013-02-11 22:34:20 +01:00
$("a.title").prepend($("< span class = 'integral' > ∫< / span > "));
$("a.title").hover(function (e) {
$(".integral").css("display", "inline");
var width = $(".integral").width();
$("a.title").css("left", -1 * width);
},
function (e) {
$(".integral").css("display", "none");
$("a.title").css("left", 0);
});
2013-10-21 21:19:31 +02:00
var newlozenge,
currentblock,
currentlink,
currentlozenge,
instructionbox = $("#integration-instruction-block"),
hashes = $('.integration-instructions').map(function() {
return this.id || null;
}).get();
function switchToIntegration(integrationHash) {
var cleanHash = integrationHash.substr(1);
if (hashes.indexOf(cleanHash) > -1) {
currentblock = $(integrationHash);
currentlozenge = $(".integration-lozenge.integration-" + cleanHash);
2016-02-23 21:04:12 +01:00
$(".integration-lozenges, .portico-page-header.extra, .portico-large-text.extra").hide();
2013-10-21 21:19:31 +02:00
newlozenge = currentlozenge.clone();
newlozenge.find(".integration-logo").unwrap();
newlozenge.addClass("integration-lozenge-static");
instructionbox.hide();
instructionbox.children(".integration-lozenge").remove();
instructionbox.children(".integration-instructions").appendTo("#integration-instructions-group");
instructionbox.append(newlozenge);
instructionbox.append(currentblock);
instructionbox.show();
$("#integration-list-link").css("display", "block");
window.scrollTo(0,0);
}
}
function updateHash () {
2016-02-23 21:04:12 +01:00
var hash = document.location.hash;
if (hash & & hash != '#hubot-integrations') {
2013-10-21 21:19:31 +02:00
switchToIntegration(document.location.hash);
}
else if (currentblock & & newlozenge) {
$("#integration-list-link").css("display", "none");
2016-02-23 21:04:12 +01:00
$(".integration-lozenges, .portico-page-header.extra, .portico-large-text.extra").show();
2013-10-21 21:19:31 +02:00
instructionbox.hide();
newlozenge.remove();
currentblock.appendTo("#integration-instructions-group");
2016-02-23 21:04:12 +01:00
$('html, body').animate({scrollTop: $(hash).offset().top}, 'slow');
2013-10-21 21:19:31 +02:00
}
}
window.onhashchange = updateHash;
updateHash();
2013-02-06 20:25:04 +01:00
});
< / script >
2013-10-21 21:19:31 +02:00
2013-02-06 20:25:04 +01:00
{% endblock %}
