Konnectify & Slack Integration

Konnectify

Description Permissions Security & Compliance

Konnectify connects Slack with more than 500 business applications, helping teams automate repetitive work, synchronize information, and receive important business updates directly in Slack.Konnectify is an integration and workflow automation platform designed for sales, customer support, marketing, finance, project management, and business operations teams. It allows users to connect Slack with the applications they already use and create automated workflows using triggers, actions, conditions, and field mappings without building custom integrations.Business information is often distributed across multiple tools. Teams may need to check different applications, copy data manually, notify colleagues, and repeat the same operational tasks throughout the day. Konnectify reduces this manual work by automatically transferring information between Slack and connected business applications.Users can create workflows that send Slack notifications when a new contact, deal, support ticket, payment, subscription, task, or other business event occurs. Workflows can also post application updates, share execution results, manage Slack channels, invite users to selected channels, and start actions from supported Slack events or commands.Users can explore available Slack integrations from the Konnectify Slack integrations page. They can search for an application, review the available workflow templates, select a template, or create a custom workflow.To connect Slack, users sign in to Konnectify, select an integration or workflow template, choose Slack during workflow configuration, and click Connect Slack. They can then select their Slack workspace, review the requested permissions, approve the connection, map the required fields, and activate the workflow.Slack authorization takes place during workflow configuration so the connection can be associated with the correct Konnectify organization, project, and workflow.After a workflow is activated, Konnectify can send automated messages and updates to the Slack channels selected by the user. These messages may include CRM updates, support ticket details, payment events, subscription changes, project activity, task updates, alerts, and workflow results.Konnectify only performs the actions configured by the user. It does not automatically create workflows, access unrelated Slack content, or post messages without an authorized Slack connection and an active workflow.Users can manage their Slack connections, workflow configurations, field mappings, execution history, and connection status from the Konnectify web application.Konnectify uses Slack OAuth and requests only the permissions required for its available Slack triggers and actions. Workflows are private by default and must be explicitly shared with authorized Konnectify project members. Personal Slack authorizations are associated with the user who connected them and are not shared with other users. When personal authorization is required, each collaborator must connect their own Slack account.Konnectify must not be used to broadly collect, archive, export, back up, or independently index Slack messages or files. Message-based workflows should only process content that the user is authorized to access and must comply with Slack workspace permissions, retention settings, administrative controls, and Marketplace policies.Konnectify helps teams reduce repetitive work, improve the flow of information between applications, and keep relevant business updates available in Slack. Once configured and activated, workflows run automatically according to the selected triggers, conditions, mappings, and actions.

Konnectify will be able to view:

Konnectify will be able to do:

Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.

General

Privacy & data governance

Data retention policy

RETENTION PERIOD OF DATA AND RECORDS The department that creates or handles each type of data and record shall define and apply the retention period for that type of data and record. While deciding the retention period, the following sequence shall be followed – Check Statutory or Regulatory or Legislative requirement of retention for each type of Data or Record, Check if any Contractual requirement exists for the retention of each type of data or record, Check Organizational policy about retention of data or records, Select the highest applicable retention period and apply it to the concerned data or record. In the case of externally provided data or records provided by an external person or entity, the retention period as specified by the external person or entity shall be referred to in addition to the above-listed sequence. The retention period defined and applied for each type of data and record shall also be applied to the backups / archival of concerned data or records. Records shall be appropriately archived during the retention period. Once applied to any data or record, the retention period may not be changed without prior approval from the Leadership Team. The retention period for all types of data and records within the organization shall be defined and documented in the prescribed format. (Ref: Annexure A - Retention Schedule)

Data archiving and removal policy

DISPOSAL / DELETION / DESTRUCTION OF DATA AND RECORDS Data and records shall be securely destroyed, deleted, or disposed of when they are no longer required or upon completion of the applicable retention period, in order to prevent unauthorized access. All electronic data and records shall be destroyed using secure methods such as permanent deletion and purge mechanisms for electronic records and storage systems. The destruction, deletion, or disposal process shall also apply to all backup copies and archived records once the applicable retention period has expired. Records relating to the destruction, deletion, or disposal of Personal Data, Personally Identifiable Information (PII), or Confidential Information shall be retained by the concerned department for audit purposes and future reference. ANNEXURE A – RETENTION SCHEDULE Application and Related Database Data shall be retained for as long as the client contract remains active. Client Personal Data (Client Master Setup in Products) Data shall be retained for three months from the date of termination of the client contract. Client End-User Data or Employee Data Within the Application Hosted on Data shall be retained for one year from the termination date of the client contract, whichever is earlier. Client Data – Files and Media Within the Cloud Data shall be retained for one year from the termination date of the client contract, whichever is earlier. Backup of Database Backups shall be retained for one month. Trial Customer Data Trial customer data shall be deleted within one month after the end of the trial period. IT Infrastructure Personal Data in Emails (Corporate Mail Server) and Other Mail Communications with Clients Emails shall be retained for a period of XX years. After this period, emails and attachments shall be permanently deleted. User Desktops and Laptops Data stored on user desktops and laptops shall be deleted only upon the employee’s exit from the company. Employee-Owned Devices Employees are encouraged not to store company data on employee-owned devices. Such devices are outside the scope of this retention policy. Personal Drives Use of personal drives is not permitted. Corporate Drives / Archives (Dropbox, OneDrive, etc.) If corporate drives or archives are used, the retention period shall be determined based on the type of data stored. Client Data – Hard Copies Offline Payroll Processing Services Input files received from clients and data entered into the application shall be retained for one month and then deleted. Output files, if any, sent to clients shall be retained for seven years or one year from the termination date of the client contract, whichever is earlier. Marketing CRM All active contacts shall be retained until they become inactive or opt out. Upon opt-out, only the minimum required information shall be retained, and all other data shall be deleted. Dormant contacts that have remained inactive for the last two years shall be deleted. Mailing list retention shall follow the same retention rules as CRM data. Opt-out lists shall be retained permanently. API Call Data API call data shall not be retained. Client Communication Client communication records shall be retained as required for operational and compliance purposes. Finance Invoices on Invoices shall be retained in accordance with statutory retention requirements applicable in the relevant jurisdiction. Client Master Data on Client master data shall be retained for as long as the client contract remains active. Website Cookie Data Cookie data shall be retained for a period ranging from 182 days to 3650 days, depending on the applicable purpose and legal requiremen

Data storage policy

PROTECTION OF DATA AND RECORDS Access to each type of data or record shall be provided based on the classification applied to it. Corresponding policies shall govern the access provision and revocation to all types of data and records. Risks for records shall be assessed, and mitigation controls shall be implemented to protect the data and records. Electronic data and records shall be protected from unauthorized access, theft, disclosure, corruption, changes, destruction, etc. Adequate provisions shall be made regarding the backup and redundancy of data and records in case of disast

App/service has sub-processors

yes

Guidelines for sub-processors

https://trust.konnectify.co/#/subProcessors/Google%20Cloud%20Platform

App/service uses large language models (LLM)

Certifications & compliance

Data deletion request procedure

Procedure for Handling Requests for Data Deletion Upon receiving a request for data deletion, the organization follows a structured process to ensure secure, compliant, and timely handling of the request. Receipt and Verification of Request All requests for deletion of Personal Data, Personally Identifiable Information (PII), or Confidential Information are formally received through authorized communication channels. The identity and authority of the requester are verified before any action is initiated. Assessment and Validation The request is reviewed to determine: The nature and scope of the data involved Applicable contractual, legal, regulatory, or statutory retention requirements Whether any data must be retained for compliance, audit, dispute resolution, or legal obligations Identification of Data Sources Relevant departments and system owners identify all locations where the data resides, including: Production systems and applications Databases File storage systems Email systems Backup and archive repositories Cloud services and integrated platforms Approval and Authorization Once validated, the deletion request is approved by the designated authority or data owner in accordance with internal policies and governance procedures. Secure Deletion and Disposal Data is securely deleted, purged, or destroyed using approved methods to prevent unauthorized access or recovery. This includes: Permanent deletion from active systems Removal from cloud storage and shared repositories Deletion of backup and archived copies, where applicable and feasible within backup retention cycles Retention Exception Handling Where legal, regulatory, contractual, or operational requirements mandate retention of certain records, only the minimum necessary data shall be retained for the required duration. Documentation and Audit Trail Records of the deletion request, approvals, actions performed, and completion status are maintained for audit and compliance purposes. Confirmation to Requester Upon completion of the deletion process, confirmation may be provided to the requester in accordance with applicable privacy regulations and organizational procedures. Periodic Review and Compliance Monitoring Data deletion activities are periodically reviewed to ensure continued compliance with applicable laws, contractual obligations, and internal retention policies.

HIPAA compliant

yes

While this app may offer HIPAA compliance, Slack does not have a business associate agreement with any third-party application providers, including those in the Slack Marketplace, so you are responsible for validating the provider's compliance and executing an appropriate agreement before enabling.

Security