Slack Vacation Tracker | Actioner App Directory





Manage and track employee leaves in Slack with Actioner. Start using the app in Slack immediately after you install it. Actioner provides an AI-powered Slack vacation tracker. Say goodbye to the stress of unaddressed time-off requests! Easily create leave policies, assign managers, and gain the power of quick and fast leave management. With Slack Time-off app, you can effortlessly track PTOs and vacations through Slack, create unlimited leave policies according to your needs, and utilize the power of AI for your leave management. ## Features - **Request leave and relax:** Easily submit your leave request directly within Slack and send a reminder to your manager until they respond. - **Plan your leaves beforehand:** Review your upcoming leaves, your leave history, and the number of leave days you have left. Access your teammates' upcoming leaves, helping you plan your own more effectively. - **Cancel your upcoming leave:** Cancel your upcoming leaves hassle-free. When you cancel a leave, the days you had requested return to your balance as if you never requested the leave in the first place. - **Create diverse leave policies:** Create a policy document within the app and assign the employees to the leave policy you want. You can define a wide range of leave types with unique limits and rules. ## How to get started To get started with the Actioner Time-off Slack app, you should follow these steps: 1. Click Add to Slack 2. Set up team structures and apply default leave policies. 3. Add your team members to the app and assign appropriate permissions. 4. Finish setting up your profile, including hiring date, to fully utilize the app's features.

Workflows

Check request history and upcoming leaves of absence

This workflow enables you to check request history and upcoming leaves of absence.

Share your leave to the leave channel

This workflow enables you to share your time-off with the leave channel.

Update employee details

This workflow enables you to update an employee's time-off-related details.

AI Agent of time-off

This workflow enables you to control AI agents. You can call the agent in your designated channel by mentioning Actioner (@Actioner).

Add used leave day(s) to employee

This workflow enables you to add used leave days to the selected employee.

Assign policy to employees

This workflow enables you to assign employees to the selected leave policy.

Remind approver to respond a request

This workflow reminds approvers to respond to their pending leave requests.

Cancel upcoming leave

This workflow enables you to cancel an upcoming leave.

Add all users in the Actioner workspace to the app as employees

This workflow enables you to add the users in Actioner workspace to the Time-off App. You can use this workflow to seamlessly integrate new employees into the app as they join your workspace later on. The workflow ensuring that only those not already added to the app are added.

Check profile

This workflow enables you to check your profile details, leave balance details, and leave history with the option to cancel upcoming leave requests.

AI agent message

This workflow is triggered when AI agent has a message in response to a user message.

Decline leave request

This workflow enables you to decline a leave request.

List leave requests of an employee

This workflow enables you to list the leave request of an employee.

Confirm the leave request

This workflow enables you to confirm a leave request after you check your day amount in the "Request leave" workflow.

AI agent thread message interaction

This workflow is triggered via thread messages in AI channel.

Approve leave request

This workflow enables you to approve a leave request.

Add a user from Actioner workspace to the app as employee

This workflow enables you to add single user from the Actioner workspace to the Time-off App.

List employees

This workflow enables you to list employees. You can list your teammates and employees that you are responsible for.

Send upcoming leaves as DM

This workflow enables you to send upcoming leaves as DMs. You can select the users who will receive DM and time period for the lookup.

Send notification to leave channel

This workflow enables you to send a notification to the leave channel one day before the leave start date.

Cancel AI conversation

Cancel an AI conversation run.

Request leave

This workflow enables you to request leave.

Send upcoming leaves to the channel

This workflow enables you to send upcoming leaves to a Slack channel. You can select the channel and time period for the lookup.

Get started

This is the setup workflow. It adds the users in Actioner workspace to the Time-off App and configures app settings. You can disable or delete this workflow after you complete the setup.

AI agent status requires action

This workflow is triggered when AI agent requires an action.

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.