GitLab by Git-Zen
GitLab by Git-Zen When a customer-reported bug lands in Zendesk, your GitLab team should be able to act on it immediately, and your support team should see every update without leaving Zendesk. Git-Zen connects both tools so the handoff is automatic, in both directions. How It Works From a Zendesk ticket, agents can: * Create a new GitLab issue in one click, with labels, milestones, assignees, and your existing issue templates * Link an existing GitLab issue to the ticket * See issue updates, commits, and comments appear automatically in the ticket timeline From GitLab, developers can: * Reference a Zendesk ticket number in a commit message. The commit and affected files appear in the ticket automatically * Leave issue comments that flow into Zendesk as public or private notes No GitLab account needed for support agents. No Zendesk access needed for developers. Key Features Create GitLab issues from Zendesk: File bugs and feature requests with labels, assignees, milestones, and weight set at creation time Commit tracking: Commits that reference a ticket appear inside Zendesk with the files they touched Epics support: Link Zendesk tickets to GitLab epics Two-way comment sync: GitLab comments appear in Zendesk; ticket comments post to GitLab Custom issue templates: Use your existing GitLab templates when creating issues from Zendesk Multiple issues per ticket: Link as many GitLab issues as needed to one ticket Auto-tagging: Zendesk tickets are automatically tagged when linked or when an issue is closed Role-based permissions: Control which agents can create or modify GitLab issues Simple per-agent pricing: $4 per Zendesk agent, per month. Unlimited tickets and integrations. Free trial included. Works with GitLab.com. Self-hosted GitLab instances are not currently supported. Security & Data Disclosure Git-Zen relays data between Zendesk and GitLab in real time: ticket subject, description, and comments are read from and written to your Zendesk account, and corresponding issue data (title, description, status, assignee, labels, and comments) is read from and written to your GitLab account, to keep both systems in sync. We store your OAuth access tokens (encrypted) and account configuration (connected GitLab account/workspace, sync settings, field mappings) on Git-Zen servers so we can act on your behalf. We do not separately retain ticket or issue content on our servers -- sync state is written back into a private custom field on the Zendesk ticket itself. Authentication uses OAuth 2.0 for both Zendesk and GitLab. For more information, visit https://www.git-zen.com
Myndbend Process Manager
Myndbend Process Manager: Policy-Driven Approval & Workflow Governance for Zendesk Myndbend™ Process Manager extends Zendesk with a structured governance layer for approvals and complex workflows. It enables teams to build custom, auditable, and policy-driven processes directly inside Zendesk—without relying on tribal knowledge or manual coordination. Organizations use Myndbend to standardize high-stakes operational workflows such as: HR Onboarding & Offboarding IT Change Management Access Rights Requests Financial Approvals Internal Escalations ...or any other workflow that requires approvals, dependencies, or coordinated downstream work. Approval Governance & Decision Controls Myndbend™ Process Manager allows you to build audit-ready approval processes that ensure the right people review the right requests with the right context. Key capabilities include: Centralized Approval Tracking: Track all approval activity directly on tickets—including comments and actions from stakeholders (e.g., Finance or Legal) who don't log into Zendesk. Enforced Authority Levels: Define staff and supervisor relationships so requests never bypass required approval hierarchies. Context-Rich Approvals: Customize approval emails to surface relevant ticket data, ensuring approvers understand impact and risk before signing off. Dynamic Approval Routing: Automatically assign approvers based on custom criteria such as department, request type, or risk level. Sequential Approvals: Enforce ordered approval flows (e.g., HR approval before IT) to match real-world policy requirements. Ticket Workflows Myndbend™ Process Manager helps teams codify policies into enforceable workflows—so no steps are skipped and no context is lost. Capabilities include: Ticket Relationships & Dependencies: Define and enforce dependencies between tickets (e.g., access cannot be granted until prerequisites are complete). Cross-Team Orchestration: Automatically create and manage child tickets for different teams (IT, HR, Facilities) when a request is approved. Standardized Templates: Turn manual best practices into repeatable, automated workflows that save time and reduce errors. Synchronized Data: Keep linked tickets in sync to maintain a consistent source of truth across the workflow. Audit-Ready Exports: Export tickets with full histories—including comments, custom fields, and approval actions—for compliance and audits. View features and pricing Data Privacy & Usage Data Accessed & Used: The application uses Zendesk OAuth for agent and end-user access to read and update tickets. It accesses data such as ticket content, comments, custom fields, and ticket-specific user data for its features (approvals, child ticket creation, etc.). Data Retention: Myndbend Process Manager permanently stores metadata and templates, but does not retain personal Zendesk ticket or user data. Ticket-specific data is immediately purged after use. Security & Compliance: The Myndbend Process Manager application is subject to an SOC 2 Type II examination covering Security, Availability, and Confidentiality. Data in motion is secured using the TLS protocol. Data Privacy: The solution limits data collection, processing data strictly for service delivery. For more information, please review our Terms of Service and Privacy Policy.
