Chatbot Overview
Conversational Bots
Intents & Entities
Intelligent Bots's Approach Conversational Platform
Bot Concepts and Terminology
Natural Language Processing (NLP)
Bot Types
Bot Tasks
Starting with Platform
How to Access Bot Builder
Working with Bot Builder
Building your first Bot
Getting Started with Building Bots
Using the Dialog Builder Tool
Creating a Simple Bot
Release Notes
Latest Updates
Older Releases
Bot Builder
Creating a Bot
Dialog Task
Working with User Intent & Dialog Node
Working with Entity Node
Supported Entity Types
Working with Composite Entities
Supported Time Zones
Supported Colors
Supported Company Names
Working with Message & Confirmation Nodes
Working with Service Node
Implementing Custom Authentication
Enabling 2-way SSL for Service nodes
Working with Script Node
Working with Agent Transfer Node
Working with WebHook Node
Defining Connections & Transitions
Managing Dialogs
Prompt Editor
Context Object
Session and Context Variables
Action & Information Task
Working with Action Tasks
Working with Information Tasks
Establishing Flows
Alert Tasks
Working with Alert Tasks
Managing Ignore Words and Field Memory
Knowledge Tasks
Building Knowledge Graph
Importing and Exporting Bot Ontology
Knowledge Extraction
Natural Language
Machine Learning
ML Model
Fundamental Meaning
Knowledge Graph Training
Ranking and Resolver
NLP Detection
NLP Settings and Guidelines
Bot Intelligence
Dialog Management
Context Management
Amend Entity
Multi-Intent Detection
Default Conversations
Channel Enablement
Test & Debug
Talking to Bot
Utterance Testing
Batch Testing
Recording Conversations
Publishing your Bot
Analyzing your Bot
Conversation Flows
Bot Metrics
Advanced Topics
Bot Authorization
Language Management
Collaborative Development
IVR Integration
Universal Bots
Enabling Languages
Smart Bots
Sample Bots
Travel Planning
Flight Search
Event Based Bot Actions
Sentiment Analysis
Tone Analysis
Sentiment Management
Bot Settings
Bot Functions
General Settings
PII Settings
Customizing Error Messages
Bot Management
API Guide
API Overview
API List
SDK Overview
SDK Configuration
SDK Security
SDK App Registration Web SDK Tutorial
Message Formatting and Templates
Mobile SDK Push Notification
Using the BotKit SDK
Installing the BotKit SDK
Events for the BotKit SDK
Functions for the BotKit SDK
BotKit SDK Tutorial – Agent Transfer
BotKit SDK Tutorial – Flight Search Sample Bot
Using an External NLP Engine
Web Socket Connect & RTM
Bot Administration
Bots Admin Console
User Management
Managing Your Users
Managing Your Groups
Role Management
Bots Management
Inviting Users
Sending Bulk Invites to Enroll Users
Importing Users and User Data
Synchronizing Users from Active Directory
Security & Compliance
Using Single Sign-On
Cloud Connector
Bot Store
Creating a Bot Account
Adding a Bot
Choosing a Channel for a Bot
Interacting with a Bot
Setting Up Web Service Alerts
Setting Up RSS Alerts
Setting Up the Webhook Bot
Custom Bots
Bots for your Customers FAQs
Bots for your Workforce FAQs
Adding Bots
Contacting Support
Setting Up Filters
Bot Store Settings
  1. Home
  2. Docs
  3. Bots
  4. Bot Store
  5. Adding Bots
  6. Adding a Wercker Bot

Adding a Wercker Bot provides integration for a built-in Wercker Bot that you can use to display message notifications and execute tasks directly from Messenger, or other supported channels. To use the Wercker Bot, you just need to add the Bot to Messenger, and then configure the settings for the Bot, such as authentication to access Wercker, and the notification messages that you want. This topic describes the Wercker built-in Bot for For more information about other Bots, see Adding Bots.

About the Bot for Wercker

DIYWerckerLogoWercker is an open automation platform for developing, building, and delivering your applications. This bot enables you to both run tests and run build processes for static applications.

Integration Type Webhook – Connect to this Bot using a webhook integration where the web application pushes message notifications in near real time.
Category Developer Tools – This Bot is available in the application in the Developer Tools category.
Channels – This Bot is available in the Messenger application.
Spark – This Bot is available in the Cisco Spark application.

Configuring Wercker 

To configure a Wercker webhook for, you must have a Wercker account with administrator access as well as API access to configure a webhook. If you don’t, you’ll need to contact the Wercker system administrator for your company. For more information, see the Documentation Overview in the Wercker documentation.
To get started configuring the webhook in Wercker, you’ll need two things:

  1. The webhook URL provided when you set up an alert in your account for each alert that you want to enable in Wercker.
  2. A valid Username and Password for an account with Wercker API access.

The webhook URL is account-specific and cannot be transferred to any other account. This means that if you configure a Wercker webhook using a test account, you will have to recreate the alert and get a new webhook URL to configure in Wercker. The following URL is an example webhook URL.

Configuring Webhook

This procedure describes the steps in Wercker to configure a webhook using a webhook URL endpoint. In Wercker, you will create a custom wercker.yml file that must be saved in your repository. If you already have a wercker.yml file in your repository, skip to step 7.

  1. Log on to Wercker, and then on the top menu bar, click Create.
  2. In the Choose a Git Provider section, select your repository type.
  3. In the Select a repository section, select the repository that you want to create a wercker.yml file for, and then click Use selected repo.
  4. In the Select owner section, select your repository account, and then click Use selected owner.
  5. In the Configure access section, select wercker will checkout the code without using an SSH key, and then click Next step.
  6. In the Setup your wercker.yml file section, copy the code and pasted into a text editor of your choice, and then save the wercker.yml file to the root of your repository where you want to add a webhook to.
  7. In the text editor for the wercker.yml file, add the following code:

             – mzp/http-notify:
    where the url parameter is set to the webhook URL for the alert.
  8. Save the file, and then commit your changes.

For more information, see Deploy in the Wercker documentation.
The following is an example of a wercker.yml file configured for a sample webhook.

box: node

      – script:
        name: echo
        code: echo
      – mzp/http-notify:

After you are connected, you can perform tasks for Wercker directly from the application and setup message notifications to get notified in the application when an event occurs in Wercker.
You can integrate a Wercker action task with To configure the Trigger Build task, click , click Trigger a Build, and then in the Perform Task dialog:

  • enter a Username
  • select an Application
  • optionally enter a Branch
  • optionally enter a Commit Hash
  • and then, optionally enter a Message.

In a team room, you can enter the @wercker triggerbuild Bot command to invoke and configure this task.
You can setup message notifications to your account using a Wercker webhook. Click , click Get notified when…, click Build Updates, and then in the Setup Task dialog:

  • click the Activate button to generate a Webhook URL.
  • copy and save the URL, or click Email Instructions to send the URL to an email account. For more information, see Configuring Wercker Webhooks.
  • optionally customize the Task Name 
  • optionally customize the Short Description
  • enable or disable Mute task notifications.

Next Steps

After the webhook is configured in Wercker, when any of the events occur in Wercker, a message is displayed on the Bots page in Messenger.