Out-of-the-box connectors

The following table lists the out-of-the-box connectors that are included in BMC Helix Integration Studio by default. These connectors are either Basic or Premium. For more information about the types of connectors, contact your sales representative.

Related topics

Finding existing connectors

Configuring connectors

Important

BMC plans to stop supporting the following PSR connectors in BMC Helix Integration Service:

Helix Ops Mgmt for PSR
ITSM for PSR
TrueSight Ops Mgmt for PSR

BMC recommends that you use the PSR capability built by using BMC Helix Intelligent Automation Open link , instead of using the PSR connectors.

For more information about the deprecation of the PSR connector, see Product announcements.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Connector name	Supported application version (Cloud and OnPremises	Purpose	Connector actions	Connector triggers	Connector type	Connector version
AR System	AR Server version 20.02 and later	Use the AR System connector for enabling integration with BMC Helix ITSM to get the required out-of-the-box or custom AR forms. For an example of how the AR System connector is used in BMC Helix Multi-Cloud Service Management, see Sending and receiving data between Remedy AR System forms and third-party applications .	Create Update Query	N/A	Basic	1.0.8
Automation Anywhere *Only for BMC Helix Innovation Studio	Automation Anywhere version 1.0.59 and later	Use the Automation Anywhere connector to automate tasks or manual flows within your application or business process in BMC Helix Innovation Studio . The Automation Anywhere Robotic Process Automation (RPA) provides the following capabilities: Reduces operating costs by executing repetitive actions without human intervention. Requires minimal or no change to the underlying business processes. Empowers the developers to automate any process. For more information, see Automating a task or a manual flow by using the Automation Anywhere connector .	Run RPA bot script	Automation status check	Basic	1.0.59
AWS Support	Latest Cloud version	Use the AWS connector to design flows that are related to support case management in your Amazon Web Services cloud computing environment. For example, you can design an Incoming Email-to-AWS flow that creates a new case in your AWS application after you receive an email in your Incoming Email account. You can use the AWS connector actions associated with cases, communication notes, services, and service categories from your AWS application.	Actions Create a new case Create a communication note Resolve a case Return a list of cases Return a list of services and service categories	N/A	Premium	1.2.7
AWS Service Catalog *Only for BMC Helix Digital Workplace Catalog integrations	All available versions	Use the AWS Service Catalog connector to integrate BMC Digital Workplace Catalog with the AWS application. The AWS Service Catalog connector has only one available action: Launch service catalog product. When the BMC Digital Workplace Advanced users request the AWS services, these services are imported from the service catalog of AWS to BMC Digital Workplace Catalog through the BMC Helix Integration Service API. Such a connection helps to reduce developmental efforts required for integrating AWS and BMC Digital Workplace Catalog directly. For more information, see Integrating BMC Helix Digital Workplace Catalog with BMC Helix Integration Service and AWS Service Catalog connector .	Launch service catalog product	N/A	Basic	1.0.3
Azure Alerts	All available Cloud versions	Use the Azure Alerts connector to design flows that are related to receiving alerts in your Microsoft Azure cloud computing service. For example, you can design an Azure Alerts-to-Slack flow. You can configure this flow to result in sending a notification about a new alert to a specified Slack channel. The Azure Alerts connector has only one trigger, such a flow starts running when you receive a new alert in your Microsoft Azure application	Update Azure alert state	New alert received	Premium	1.1.4
Azure DevOps *Supported only with default cloud site. Not supported for on-premises sites.	All available Cloud versions	Use the Azure DevOps connector to design flows that are related to work items in your Azure DevOps project planning tool. For example, you can design a JIRA-to-Azure DevOps flow that creates a comment on a work item in Azure DevOps after an issue is updated in a related JIRA project.	Create a new work item Create comment on a work item Query work item by tag	New comment on work item in project New or updated work item in project	Premium	1.0.4
Basecamp	Basecamp API version 1.0	Use the Basecamp connector to design flows that are related to multiple project activities and project artifacts in your Basecamp project management tool. For example, you can design a Basecamp-to-JIRA flow that creates a new issue in your JIRA application after a new to-do list is created in your Basecamp project. You can create multiple flows associated with calendars, events, projects, messaging, to-do lists, accounts, and documents in your Basecamp application.	Actions Create a new calendar Create a new calendar event Create a new calendar event in a project Create a new message in a project Create a new project Create a new text document in a project Create a new to-do item in a to-do list Create a new to-do list in a project Grant access to a project Upload a file to a project	Triggers New or updated account New or updated activity in project New or updated calendar event New or updated calendar event on project New or updated calendar in account New or updated comment in project New or updated file in project New or updated people in account New or updated project in account New or updated text document in project New or updated to-do item in to-do list New or updated to-do list in project	Basic	1.0.1
BMC Helix Business Workflows	All version of BMC Helix Business Workflows	Use the BMC Helix Business Workflows connector to design flows that are related to case management and task management in your BMC Helix Business Workflows application. You can design flows that are triggered when cases or external tasks are created or updated. You can also design flows that result in creating or updating cases or external tasks. For example, you can design a BMC Business Workflows-to-Slack flow that sends a message to a specified Slack channel after an external task is updated in your BMC Business Workflows application. For more information about using this connector, see Integrating BMC Helix Business Workflows with other applications .	Actions Add an activity to a case Add an activity to a task Add an external task to a case Create a new case Update a case Update an external task	New or updated case New or updated external task	Basic	1.5.2
CA Agile Central	Rally Web API version 2	Use the CA Agile Central connector to design flows that are related to important updates in your CA Agile Central (Rally Software) project management tool. You can design flows that are triggered when CA Agile Central items are created or updated. You can also design flows that result in creating or updating the CA Agile Central items. For example, you can design a Basecamp-to-CA Agile Central flow that updates an existing task in CA Agile Central after a new comment is received in a Basecamp project. Important: For the CA Agile Central connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors.	Actions Add a discussion to a user story, task, or defect Create a new defect Create a new task Create a new user story Query artifact (user story, task, defect) by tag field Update existing defect Update existing task Update existing user story	Triggers New comment New iteration New or updated defect New or updated task New or updated user story New project New release	Premium	1.1.9
GitHub	Github API version 3	Use the GitHub connector to design flows that are related to issues in your GitHub repository hosting service. You can design flows that are triggered when issues are updated in GitHub, as well as flows that result in creating or updating issues in GitHub. For example, you can design a GitHub-to-SMTP Email flow that sends an email in your SMTP Email account after an issue is updated in GitHub.	Create a new issue Update an existing issue	New or updated issue on repository	Basic	1.1.0
Gmail	Gmail API version 1	Use the Gmail connector to design flows related to email services. The Gmail connector has only one available action: Send an email. You can design multiple flows that result in sending emails after specified triggering events take place in the source applications. For example, you can design a Slack-to-Gmail flow that sends an email after a new message is received in a Slack channel.	Send an email	N/A	Basic	1.0.7
Helix Ops Mgmt for PSR See note on connector availability	BMC Helix ITSM RestAPI version 1.0	Use the Helix Ops Mgmt for PSR connector to execute the Proactive Service Resolution (PSR) integration cases. For more information about PSR, see Proactive Service Resolution for automatic incident management with BMC Helix Integration Service and Use case: Automatic incident management. For more information about setting up PSR, see Setting up Proactive Service Resolution to enable automatic incident management. Important: For the Helix Ops Mgmt for PSR connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors.	Create/update a new/existing event	New or updated event webhook subscription	Basic	0.0.14
IBM QRadar	Version 7.3.2.x	Use the IBM QRadar connector to track security vulnerabilities as security incidents in BMC Helix ITSM to get them resolved and remediated. You can use the connector actions and triggers associated with offenses. An o ffense includes alert information generated by the IBM QRadar Security Information and Event Management (SIEM) application. For example, you can design an IBM QRadar-to-ITSM flow that creates an incident in BMC Helix ITSM when a new offense is created in IBM QRadar SIEM. For more information, see Enabling prebuilt integration with IBM QRadar .	Create offense note Update offense	New or updated offenses	Premium	1.0.2
Incoming Email	NA	Use the Incoming Email connector to design flows related to email services. The Incoming Email connector has only one available trigger: Receive an email. You can design multiple flows that are triggered after emails are received in your Incoming Email account. Additionally, you can define special conditions that trigger such flows to run. For example, you can design an Incoming Email-to-Basecamp flow that creates a new message in a Basecamp project after you receive an email with the project name as the subject in your Incoming Email account. Important: The Incoming Email connector does not need authentication to connect to a third-party system. While configuring this connector, you do not need to create a connector account.	N/A	Receive an email	Basic	1.0.1
Integration Service	Current version of BMC Helix Integration Service	Use the Integration Service connector to design flows for tracking events that take place in the BMC Helix Integration Studio application. You can design flows that monitor the statuses of other flows in BMC Helix Integration Studio or are triggered due to the flow-related errors. You can also design flows that result in performing actions related to other flows in BMC Helix Integration Studio. For example, you can design an Integration Service-to-JIRA flow that adds a comment to a JIRA issue after a specific flow is resumed in BMC Helix Integration Studio. Additionally, use the Integration Service connector for troubleshooting. BMC Helix Integration Studio provides the out-of the box Send Error Notification catalog flow that sends an email notification to your SMTP email account whenever an error occurs in BMC Helix Integration Studio. For more information, see Troubleshooting flow issues. Important: The Integration Service connector is available only to tenant administrators. End users do not see this connector in the list of available connectors and cannot use it.	Actions Activation approval response Flow activation approved Flow activation rejected Flow publication approved Flow publication rejected Publication approval response	Triggers A flow was activated A flow was created A flow was deactivated A flow was deleted A flow was modified A flow was paused A flow was published to the catalog A flow was resumed A flow was unpublished from the catalog Activation approval pending on a flow Activation approval rejected on a flow An error occurred on a flow run Publication approval pending on a flow Publication approval rejected on a flow	Basic	1.0.4
ITSM	All Cloud and OnPremises version of BMC Helix ITSM	Use the ITSM connector to design flows that are related to work items in your BMC Helix ITSM application. You can use the connector actions and triggers associated with worklog entries, change requests, incidents, problems, people profiles, and so on. For example, you can design an ITSM-to-SMTP Email flow that sends an email in your SMTP Email account after a person profile is updated in BMC Helix ITSM. Important: For the Helix ITSM / Remedy connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors. For the Helix ITSM/Remedy connector, the polling logic is set up to ensure that it is always processing a full seconds worth for the last second of records processed as follows: Records are retrieved with the modification date > the last update date from the previous polling cycle (first time through goes back 1 minute) and < current time - 1 second. The last modification date is picked up from the retrieved records and is kept as the last update date. In case there is a clock skew, if the last record retrieved is within 2 seconds of the end time, the saved last update date is set to the modified date of that record - 1 second, and any records after that time are ignored in this polling cycle, so that they can be processed in the next polling cycle. The last update date is saved for the next polling cycle.	Actions Add a new change worklog entry Add a new problem worklog entry Add a new worklog entry Add a new work order worklog entry Create a new change request Create a new incident Create a new person profile Create a new problem Create a new work order Retrieve an existing business service by name Retrieve an existing change request Retrieve an existing CI by name Retrieve an existing person profile Retrieve a shared application properties by name Update an existing change request Update an existing incident Update an existing person profile Update an existing problem Update an existing work order	Triggers New or updated change request New or updated change worklog entry New or updated change worklog entry with author information New or updated incident New or updated incident worklog entry New or updated incident worklog entry with author information New or updated outage New or updated person profile New or updated problem New or updated problem worklog entry New or updated problem worklog entry with author information New or updated work order New or updated work order worklog entry New or updated work order worklog entry with author information	Basic	1.8.5
ITSM for PSR See note on connector availability	All Cloud and OnPremises version of BMC Helix ITSM	Use the ITSM for PSR connector to execute the Proactive Service Resolution (PSR) integration cases. For more information about PSR, see Proactive Service Resolution for automatic incident management with BMC Helix Integration Service and Use case: Automatic incident management. For more information about setting up PSR, see Setting up Proactive Service Resolution to enable automatic incident management. Important: For the ITSM for PSR connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors.	Create or update incident Update incident with event information	New or updated incident	Basic	0.3.3
Jenkins	All versions	Use the Jenkins connector to design flows that are related to job statuses in your Jenkins automation server. The Jenkins connector has only one available trigger: Updated job status. You can design flows that start running after a job status is updated in Jenkins. For example, a Jenkins-to-Slack flow can send a notification about a job status update to a Slack channel.	N/A	Updated job status	Basic	1.0.3
JIRA	All versions	Use the JIRA connector to design flows that are related to projects, issues, and comments in your JIRA project management tool. For example, you can design a Slack-to-JIRA flow that adds a comment on a JIRA issue after you receive a message in a Slack channel related to the same project. Important: For the JIRA connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors .	Actions Add a comment on an issue Add an attachment on an issue Create a new issue Query issues by labels field Update an existing issue	New comment on issue in project New or updated issue on project New project is created	Premium	1.3.10
JIRA Service Desk	All Cloud versions	Use the JIRA Service Desk connector to design flows related to issues and comments in your JIRA Service Desk application. For example, you can design a JIRA Service Desk-to-Gmail flow that results in sending an email after an existing issue is updated in JIRA Service Desk. Important: BMC Helix Integration Studio supports passing attachment files from the JIRA Service Desk comments. For the JIRA Service Desk connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors .	Actions Add a comment on an issue Add an attachment on an issue Create an issue in a project Update an existing issue	New comment on issue in project New or updated Issue on project	Premium	1.0.13
Multi-Cloud	BMC Helix Multi-Cloud Broker version 21.02	Use the Multi-Cloud connector to design flows that are related to work items in your BMC Helix Multi-Cloud Service Management tool. You can use the connector actions and triggers associated with changes, worklogs, incidents, problems, and similar artifacts in BMC Helix Multi-Cloud Service Management. For example, you can design a JIRA-to-Multi-Cloud flow that updates an incident in Multi-Cloud after an issues is updated in a related JIRA project. Important: For the Multi-Cloud connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors .	Actions Create change Create change worklog Create flow transaction error Create incident Create incident worklog Create or update service unavailability Create problem Create problem worklog Create service notification Create vendor ticket data Create worklog Create workorder Query vendor ticket data Update change Update incident Update problem Update vendor ticket data Update workorder	Triggers New or updated change records New or updated incident New or updated problem records New or updated work order records New worklog record created	Basic	2.3.5
Nagios	All versions	Use the Nagios connector to design flows that are related to changes in the states of services and hosts in your Nagios monitoring and alerting service. For example, you can design a Nagios-to-Slack flow that sends a notification to a Slack channel after a state of a monitored host in a host group is changed. Important: The Nagios connector does not need authentication to connect to a third-party system. While configuring this connector, you do not need to create a connector account.	Change state of monitored host Change state of monitored service on a host	Triggers State changed for monitored host State changed for monitored host in host group State changed for monitored service in a host group State changed for monitored service in a service group State changed for monitored service on a host	Basic	1.0.1
Remedyforce	JSForce version 1.3.1	Use the Remedyforce connector to design flows that are related to important updates in your BMC Remedyforce IT service management application. You can design multiple flows that are triggered when important updates occur in Remedyforce, or flows that result in creating or updating the Remedyforce items. For example, you can design a JIRA-to-Remedyforce flow that creates a new task in Remedyforce after a new project is created in JIRA. Important: For the Remedyforce connector, you can add the sandbox or default configuration. By using the sandbox configuration, you can connect to a test Remedyforce instance. By using the default configuration, you can connect to a production Remedyforce instance. For the Remedyforce connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors .	Actions Create a new broadcast Create a new change request Create a new incident Create a new incident history Create a new problem Create a new problem history Create a new release Create a new task Update an existing broadcast Update an existing change request Update an existing incident Update an existing problem Update an existing release Update an existing task	Triggers New or updated broadcast New or updated change request New or updated incident New or updated incident history New or updated problem New or updated problem history New or updated release New or updated task	Basic	1.1.3
Salesforce	JSForce version 1.3.1	Use the Salesforce connector to design flows that are related to multiple events in your Salesforce CRM application. You can use the connector actions and triggers associated with accounts, assets, campaigns, cases, contacts, contracts, events, leads, and similar Salesforce items. For example, you can design an Integration Service-to-Salesforce flow that creates a new event in Salesforce after a flow is published to the catalog in BMC Helix Integration Studio. Important: For the Salesforce connector, you can add the sandbox or default configuration. By using the sandbox configuration, you can connect to a test Salesforce instance. By using the default configuration, you can connect to a production Salesforce instance. For the Salesforce connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors .	Actions Create a new Account Create a new Asset Create a new Campaign Create a new Case Create a new Contact Create a new Contract Create a new Event Create a new Lead Create a new Note Create a new Opportunity Create a new Order Create a new Product Create a new Solution Create a new Task Create a new User Update an existing Account Update an existing Asset Update an existing Campaign Update an existing Case Update an existing Contact Update an existing Contract Update an existing Event Update an existing Lead Update an existing Note Update an existing Opportunity Update an existing Order Update an existing Product Update an existing Solution Update an existing Task Update an existing User	Triggers New or updated Account New or updated Asset New or updated Campaign New or updated Case New or updated Contact New or updated Contract New or updated Event New or updated Lead New or updated Note New or updated Opportunity New or updated Order New or updated Product New or updated Solution New or updated Task New or updated User	Basic	1.1.1
Service Cloud	JSForce version 1.9.1	Use the Service Cloud connector to design flows that are related to customer support procedures in your Salesforce Service Cloud management tool. You can use the connector triggers and actions associated with accounts, cases, contacts, content versions, notes, users, comments, and documents. For example, you can design a Salesforce Service Cloud-to-Slack flow that sends a notification in a Slack channel after a new note is created in your Salesforce Service Cloud application. Important: For the Salesforce Service Cloud connector, you can add the sandbox or default configuration. By using the sandbox configuration, you can connect to a test instance of Salesforce Service Cloud. By using the default configuration, you can connect to a production instance of Salesforce Service Cloud. For the Salesforce Service Cloud connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors .	Actions Create a new account Create a new case Create a new case comment Create a new contact Create a new content version Create a new feed comment Create a new note Create a new user Update an existing account Update an existing case Update an existing case comment Update an existing contact Update an existing feed comment Update an existing note Update an existing user	Triggers New or updated account New or updated case New or updated case comment New or updated contact New or updated content document New or updated feed comment New or updated note New or updated user	Premium	1.0.7
Slack	All versions	Use the Slack connector to design flows that are related to messaging in your Slack collaboration tool. You can design flows that are triggered when new messages are received in the specified Slack channels. Alternatively, you can design flows to post messages to the specified Slack channels. For example, you can design a Salesforce-to-Slack flow that posts a message in a a Slack channel after a lead is updated in your Salesforce application.	Post new message In a channel	New message in a channel	Basic	1.1.6
SMTP Email	Nodemailer version 4.4.1	Use the SMTP Email connector to design flows that are related to mailing in your SMTP Email provider. The SMTP Email connector has only one available action: Send an email. You can design multiple flows that result in sending emails after specified triggering events take place in the source applications. For example, you can design a Slack-to-SMTP Email flow that sends an email after a new message is received in a Slack channel. Important: The SMTP Email connector does not need authentication to connect to a third-party system. While configuring this connector, you do not need to create a connector account.	Send an email	N/A	Basic	1.0.6
TrueSight Ops Mgmt	BMC TrueSight Operations Management version 10 and later	Use the TrueSight Ops Mgmt connector for integrations with the BMC Truesight Operations Management performance monitoring and event management tool. You can use the connector actions and triggers associated with events in BMC Truesight Operations Management. For example, you can design a TrueSight Ops Mgmt-to-Slack flow that sends a notification in a Slack channel after a new event is created in your BMC TrueSight Operations Management application. Important: The TrueSight Ops Mgmt connector does not need authentication to connect to a third-party system. While configuring this connector, you do not need to create a connector account.	Create a new event Update an existing event	New or updated event	Basic	1.0.5
TrueSight Ops Mgmt for PSR See note on connector availability	BMC TrueSight Operations Management version 10 and later	Use the TrueSight Ops Mgmt for PSR connector to execute the Proactive Service Resolution (PSR) integration cases. For more information about PSR, see Proactive Service Resolution for automatic incident management with BMC Helix Integration Service and Use case: Automatic incident management. For more information about setting up PSR, see Setting up Proactive Service Resolution to enable automatic incident management. Important: For the TrueSight Ops Mgmt for PSR connector, you can generate a custom schema while adding or updating a configuration. For more information, see Generating custom schema for connectors.	Create a new event Update an existing event	New or updated event webhook subscription	Basic	2.6.10

Out-of-the-box connectors

Comments