Hornbill iBridge
Home > Integration > Business Process Automation & Orchestration > Hornbill iBridge
IntroductionHornbill Provides its own out of the box integrations with various cloud providers as part of our Integration Bridge service (iBridge), The Hornbill iBridge allows you to integrate Automated tasks within a Business Process without the need to install or configure any on premise software or make any firewall changes. No additional configuration is required for the Hornbill iBridge out of the box you will have access to our catalog of various integrations detailed here, new integrations can be requested on the Hornbill Forum and if accepted will be made available as part of our Continuous Delivery model. All Hornbill iBridge automations are provided with simple to use input and outputs that can easily be mapped into an existing Business Process with a completely code less design. |
Related Articles |
Hornbill iBridge Provides over 400 integrations across 16 different vendors out of the box, if we do not provide an integration method or integration with a service you need then you can raise a request on our forum, we would like our customers to challenge us to provide all the necessary integrations they need from Hornbill Out of the Box and not require costly on site software deployments or consultancy.
Integration Services
The following Cloud Services are supported within the Hornbill iBridge:
- Amazon AWS
- Atlassian Jira Cloud
- BMC Remedyforce
- Cloudflare
- Freshbooks
- Freshdesk
- Freshservice
- GitHub
- Google Apps
- Google Translate
- Hornbill
- IFTTT
- Jive
- Pipedrive
- SalesForce
- Scoro
- ServiceNow
- Slack
- Yammer
- ZenDesk
Secure Credential Storage
Most Hornbill iBridge integrations will require some form of Authentication, Hornbill provides a secure credential storage KeySafe which securely stores login credentials for all of the Hornbill iBridge Services.
Integration Examples
==Twitter==
In this example, we will choose and configure the Twitter account from which we wish to send a tweet. We'll need to specify using KeySafe the Twitter account and authentication details and authorize the Hornbill app to utilize this twitter account.
Through the business process designer we can then use the Integration Call node to decide where and how often we want to utilize the Twitter integration, configuring the input parameters on each occasion, allowing if required to use different Twitter Accounts via different KeySafe configurations and different messages through the specific input parameters on each Integration Call node.
In this example we will simply use one Twitter account, and define the message to tweet to include variables from the request the business process is running against.
Finally we'll use an output parameter to write the URL of the tweet to the timeline of the request, this is not a required step but is useful for demonstration purposes or even to act as an audit trail
==Slack==
In this example, we will choose and configure the Slack account to which we want to post a message. We'll need to specify using KeySafe the Slack account and authentication details and authorize the Hornbill app to utilize this Slack account.
Through the business process designer we can then use the Integration Call node to decide where and how often we want to utilize the Slack integration, configuring the input parameters on each occasion, allowing if required the use of different Slack Accounts via different KeySafe configurations and different messages through the specific input parameters on each Integration Call node.
In this example we will simply use one Slack account, and define the message, and channel to post to including variables from the request the business process is running against.
Finally we'll use an output parameter to write the URL of the Slack Channel to the timeline of the request, this is not a required step but is useful for demonstration purposes or even to act as an audit trail.