GitHub Slack Integration for Actions Workflows





Run GitHub Actions workflows and track their statuses in Slack with Actioner. Start using the app in Slack immediately after you install it. Actioner provides a seamless GitHub Actions workflows Slack integration allowing yout to track code deployments in GitHub live from Slack to increase productivity and transparency. Enable quick error handling, more stable, reliable code through promoting public accountability within your DevOps team. ## Features - **Run GitHub Actions directly in Slack:** Use /actioner command in Slack and choose the GitHub Action you want to run from the list. Ship code faster by running your workflows right in Slack! - **Live status notifications:** Whenever you trigger a GitHub Action, Actioner sends a notification to your preferred Slack channel. You can improve your deployments and easily identify code errors by tracking the status. - **Subscribe to the GitHub events:** Once you subscribe to GitHub repositories, Actioner notifies you in your preferred channel when a workflow runs in those repositories. ## How to get started 1. Click Add to Slack. 2. Connect to your GitHub instance & subscribe to GitHub events to create a webhook. 3. Choose which channel to receive event notifications on. 4. After succesfull setup, type /github-actions in any message box in Slack to run a GitHub Action. From the list, find the GitHub Action you want to trigger. In the appearing form, choose a repository and branch. Actioner will dynamically generate the other fields. Then click **Run**. When your GitHub Action is triggered, Actioner will send messages to the Slack channel informing its live status (in progress, successful, or failed), and keep you informed throughout.

Workflows

Delete Slack user record

This workflow automatically deletes the used Slack user records.

Run workflow

This Actioner workflow allows you to invoke any GitHub workflow in your selected repository with automatically generated parameters.

Delete Slack channel record

This workflow automatically deletes the used Slack channel records.

Create workflow

This Actioner workflow allows you to create a dedicated Actioner workflow for a GitHub Actions workflow you select.

Select channel for workflow runs

You can use this workflow to select a Slack channel to send the run results of a selected GitHub workflow.

List unsubscribed workflows

Run this workflow to list the workflows that don't have subscriptions yet. If you want to receive workflow run result messages from a selected Slack channel, you can easily subscribe to them from the results list.

Remove workflow subscription

This workflow allows you to unsubscribe the selected workflow run results. When you remove the subscription, run results will no longer be posted to the selected Slack channel.

List subscribed workflows

Run this workflow to list the workflows that have subscriptions. If you want to stop receiving workflow run result messages from a selected Slack channel, you can easily unsubscribe them from the results list.

Subscribe to workflow runs

This workflow creates a webhook subscription for the workflow runs and jobs of the selected repository. Following the subscription, you will receive DM notifications for GitHub workflow runs you have started. Note that you must have the permission to create a webhook in your selected repo to be able to subscribe to workflow runs.

Listen workflow job events

This workflow sends thread messages for the each workflow job state when a run is started.

Listen workflow run events

This workflow is triggered when a workflow run is started. If the workflow run is initiated by a user, it sends a direct message to the user. Also, if the workflow is subscribed to a Slack channel, an informative message will be also sent to the channel.

Security & Compliance

Privacy & data governance

Data retention policy

For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. How long we keep your data prior to the deletion of data or termination of the contract between the customer and Actioner depends on the type of data, as described in further detail below:

Account data: Personal data that relates to customers’ relationship with the Actioner, including your workspace details, user accounts and your billing information. We retain your account information for as long as your account is active. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information for Service improvement and development, we take steps to eliminate information that directly identifies you, and we only use the information to uncover collective insights about the use of our Services, not to specifically analyze personal characteristics about you.

Configuration data: Any configuration or personal data that is required by Actioner to be functional for the customer, such as (a) applications and their sub-configurations like workflows, documents or functions, (b) credentials, connections and integrations with the third party providers, (c) identity and access management related personal data. Actioner stores and processes configuration data for the permitted purposes until the customer elects to delete such configuration data via the service and the customer is solely responsible for deleting configuration data.

Usage data: (a) Inputs, requests and form data provided by the end users or clients of the customer, (b) any data that is programmatically, periodically or automatically received through an integration of the customer, (c) any content stored as a result of processing a configuration data, (d) activity logs used to identify the source of service requests. Actioner deletes any stored usage Data sixty (60) days after the data is produced.

Data archiving and removal policy

For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. Whenever a user account is deleted by a workspace admin, Actioner automatically deletes all data stored within the context of the deleted user account like profile information and the credentials / connections for the third party integrations. Whenever an app is deleted by an app admin, Actioner automatically deletes all data stored within the context of the app like tables, records, workflow, docs, files, etc. Whenever the workspace deletion is initiated by a workspace admin, Actioner automatically deletes all data stored within the context of workspace after a waiting period of 72 hours. After the waiting period, the deletion may take up to 10 days after the termination effective date. When any data is deleted, the archived copy of the data on Actioner’s backup systems will remain for 30 days and the backup data will be securely isolated and protected from any further processing, except as otherwise required by applicable law or regulation.

Data storage policy

At Actioner, ensuring the security of our users' data is paramount. To this end, we employ robust cryptography policies and practices. All data stored within our systems is encrypted at rest using the AES256 encryption standard, providing an additional layer of protection against unauthorized access. Furthermore, we uphold strict encryption standards for data in transit, both within our internal networks and over public channels. All data transmissions utilize TLS1.2 or higher encryption protocols, safeguarding information from interception or tampering. In terms of cryptographic key management, we rely on the AWS Key Management Service (KMS) for secure and controlled handling of cryptographic keys. This includes secure key generation, restricted access, secure storage, regular backups, and periodic rotation of keys. Our integration with AWS services streamlines the encryption process and enhances control over access to keys, thereby bolstering the overall security of our platform.We operate a comprehensive backup program at Actioner. This includes our internal systems, where our backup measures are designed in line with system recovery requirements. With respect to our cloud services, and specifically referring to you and your application data, we also have extensive backup measures in place. Our data backups are retained for 30 days with support for point-in-time recovery and are encrypted using AES-256 encryption.

Data center location(s)

United States

Data hosting details

Actioner is a cloud-native product whose infrastructure is hosted on industry-leading cloud provider Amazon Web Services (AWS). Actioner cloud services and data are hosted on Amazon Web Services (AWS). Where all our computing, messaging, network, and storage layers are located in the US West, our browser application is distributed via our CDN network all over the world. As a design standard, all Actioner services as well as the upstream computing, messaging, network and storage services are running on multiple availability zones (AZs) so that the traffic and the data are distributed among them. This design allows us to tolerate zone-specific failures with no downtime. This multi-zone high availability is the first line of defense for geographic and environmental risks and means that services running in multi-AZ deployments should be able to withstand AZ failure.