Other Integrations

Besides GitHub, GitLab, Azure DevOps, Jira, and Linear, Git-Zen connects Zendesk to Trello, ClickUp, Notion, monday.com, and Asana. These integrations are newer, and they have less documentation. This page covers what is different for each one.

What all five have in common

• Full version only. There is no Lite app. See Plans and billing.
• OAuth only. You cannot use a personal access token.
• Same sidebar. You create, link, unlink, and comment on items the same way as on other platforms. See Creating and linking issues.
• Reference tags. Git-Zen finds the Zendesk ticket by a gz# reference tag on the item. Where it looks depends on the platform (see below).
• No attachments on new items. Git-Zen does not send ticket attachments when it creates an item.
• Outgoing comments. Send comments to linked issues works for all five.

Closed items

Zendesk Ticket Tags when Issue Closed and Solve Zendesk ticket when issue is closed work for all five. What counts as closed depends on the platform:

• Trello: the card is archived. Moving a card to a “Done” list does not count.
• ClickUp: the task moves into a status of type closed or done.
• Notion: the page’s Status property moves into the Complete group. Notion also treats the Canceled group as closed. A page that was already complete when you linked it does not count.
• monday.com: the item’s status moves to the label that the board marks as done, usually Done. If monday.com does not send the done flag, Git-Zen checks for the label text “Done”.
• Asana: the task is marked complete.

See Zendesk tags.

Install and authorize

1. Install the Git-Zen app for your platform from the Zendesk Marketplace.
2. Authorize Zendesk. See Installing Git-Zen from Zendesk.
3. Git-Zen opens your platform’s authorization screen. Sign in and approve.

If you cannot authorize the platform yourself, the authorization page gives you an email to send to your platform administrator.

Trello

• Repository equivalent: a board.
• Authorization: Trello’s token flow. Git-Zen requests read, write, and account access. The token does not expire.
• Webhooks: Git-Zen creates one webhook for each board that you check on the Webhooks screen.
• Reference tag: in the card description. When you link a card, Git-Zen also adds the ticket URL to the card as an attachment.
• What reaches Zendesk: card created, changed, moved to another list, members and labels changed, deleted, and comments added, edited, or deleted. Comment filters apply.

ClickUp

• Repository equivalent: a list, shown as Space / Folder / List.
• Authorization: ClickUp OAuth.
• Webhooks: Git-Zen creates one webhook for your workspace when you authorize.
• Reference tag: in the task description.
• What reaches Zendesk: status, priority, assignee, tag, name, and due date changes, and comments added, edited, or deleted. Comment filters apply.
• Limits: Git-Zen cannot reach lists that the authorizing user cannot access.

Notion

• Repository equivalent: a database. You choose which databases Git-Zen can use on Notion’s screen during authorization. To add a database later, authorize again.
• Authorization: Notion OAuth. Notion sets the permissions on its own screen.
• Webhooks: you do not set up webhooks. Git-Zen receives Notion events for your workspace.
• Reference tag: Git-Zen adds a gz# paragraph to the page body when you link a page. Unlinking does not remove it.
• What reaches Zendesk: page created, changed, moved, or deleted, and comments added, edited, or deleted. Comment filters apply.

monday.com

• Repository equivalent: a board.
• Authorization: first install the Git-Zen app in your monday.com account. An account admin may need to approve it. Then authorize. The token does not expire.
• Webhooks: Git-Zen creates webhooks for each board that you check on the Webhooks screen.
• Subitems: subitem events arrive through the parent board. To sync subitems, check the parent board. monday.com does not allow webhooks on a “Subitems of …” board, so Git-Zen does not list those boards.
• Reference tag: in the item name or in an update. monday.com items have no description, so Git-Zen adds the gz# tag as an update when you link an item.
• What reaches Zendesk: item created, column changes (including status), renamed, archived, deleted, or restored, and updates. The same events for subitems also reach Zendesk. Git-Zen always adds these as private comments.

Asana

• Repository equivalent: a workspace. When you create a task, you also choose a project.
• Authorization: Asana OAuth. Git-Zen renews the token automatically.
• Webhooks: Git-Zen creates one webhook for each workspace that you check on the Webhooks screen.
• Reference tag: in the task name or notes.
• What reaches Zendesk: task created, completed, reassigned, renamed, due date changed, removed, or restored, and new comments. Comment edits do not reach Zendesk.

Tag/label pairs

The Tag/Label Sync screen appears for these integrations. Field mappings apply for Notion. Field sync does not work yet for Trello, ClickUp, monday.com, and Asana.

If you saved Notion mappings before release 3.2.11.0 and they do not apply, contact support.

If you need help with any of these integrations, contact support.