How integrations work

Drobber can send each project’s comments to the tools your team already works in. Slack and Microsoft Teams post a message in a channel. Jira, Linear, GitHub, ClickUp, Trello, Asana, monday.com, Notion, Basecamp and Teamwork.com get one task, issue or card per comment, kept up to date as the comment changes. Zapier and Make connect Drobber to thousands of other apps, both ways.

Claude is connected from the same page but has its own guide: see Connect Claude.

Where to find it#

• The Integrations page: open the menu under your name and choose Integrations. Tools are connected here once for every project. Team members can open it; clients can’t.
• A project’s Settings tab, under Connected tools: choose where that project’s comments go, or connect the project to a tool with an account of its own.

A tool shown blurred under a Coming soon note is not available yet: it can’t be connected, and nothing is sent to it.

Who can do what#

• The workspace owner connects and disconnects a tool for the whole workspace. Everyone else sees "Not connected. Ask the workspace owner to connect it here."
• Any team member who can open a project can turn a connected tool on or off for it, change where its comments go, or connect the project to a tool with its own account.
• Zapier and Make work with a key each person makes for themselves. See Connect Zapier.

Connect a tool#

1. Open the menu under your name and choose Integrations.
2. Find the tool and press its Connect button, such as Connect Jira. Most tools connect in one click: you approve Drobber in the tool, and come back to Drobber. If you’d rather use a token, open Use a token instead.
3. For tools that take a token, follow the short instructions on the card, paste in what it asks for and press Connect. Drobber checks the details work before saving them (the button says Checking...).
4. Turn it on for each project and choose where its comments go: a channel, project, list, board, repository or database, depending on the tool.

Connected tools show Connected for the workspace. Tools marked Two-way bring status changes back to Drobber. Credentials are stored encrypted.

What is sent#

Drobber sends four things: a new comment, a reply, a status change and, for tools with an assignee, a change of assignee. It sends them for every comment, whether it was left on the site, by a visitor through visitor feedback, on a PDF, image or video, through Zapier or Make, or by Claude.

Each comment gets one item, made when the comment is left. Comments that were already there when you turned a tool on are not sent. A reply on one of them makes its item then; a status change on one sends nothing.

What each item contains#

• Title: the comment’s number and the start of its text, such as "#12: The logo looks blurry on the home page".
• The comment’s text.
• Who left it, on which page, in which project. Visitor comments say "From a visitor to the live site" with their email, if they gave one.
• Where it was seen: browser, operating system, device and window size.
• Its comment type, and the suggested text edit or highlighted text, if there is one.
• View it on the page: a link to the page. Open in Drobber: a link to the comment.
• Up to three screenshots from the comment itself (not its replies), in tools that take them.
• The console errors, the element and the environment, when the project’s Testing tools are on and the comment has developer details. See Testing tools.

If the comment is already Feedback or Resolved when its item is made, the item starts in that stage too.

How statuses match#

Drobber has three statuses: In Progress, Feedback and Resolved. In a tool with stages, it looks for one with a matching name:

• In Progress: a stage named like "In progress", "Doing", "Working", "Active", "Started" or "WIP".
• Feedback: a stage named like "Feedback", "Review", "Waiting", "Client", "Approval", "Check", "QA" or "Testing".
• Resolved: a finished stage, preferring one named "Done", "Complete", "Resolved", "Closed", "Finished", "Shipped" or "Live".

When there is no matching stage, Drobber closes or reopens the item the tool’s own way and adds a comment on it, such as "Status: Feedback". See Comment statuses.

What comes back#

Tools marked Two-way (all except Slack and Teams) bring status changes back. Move a card to Done and the comment is resolved; reopen it and the comment reopens. Drobber adds a reply on the comment saying why, such as "Marked "Done" in Jira, so this is resolved." or "Moved to "Review" in Jira, so this is waiting on feedback."

• A finished stage becomes Resolved, a stage named for feedback or review becomes Feedback, and anything else becomes In Progress.
• Most tools tell Drobber the moment something changes. Otherwise Drobber checks every three minutes. The project’s Connected tools says which: "come back instantly" or "come back within a few minutes".
• Only changes made in the tool since Drobber last looked count, so a status you change in Drobber is never undone.
• A status that comes back is passed on to your other connected tools, Slack, Teams, Zapier and Make, but not back to the tool it came from.
• Comments and assignee changes made in the tool come back only from ClickUp. See Connect ClickUp.
• Archived projects are not checked, and Drobber checks up to 300 linked items per connection each time.

Drobber doesn’t show a link to the item on the comment; each item links back to its comment with Open in Drobber.

When something fails#

Sending is best effort: a tool being down never stops a comment being saved. A project’s comments go out in order, and failures show on the Integrations page ("Failing:" and the error, with a count such as "1 failing") and in the project’s Connected tools ("Last attempt failed:"). See Comments aren’t reaching a connected tool.

Plans#

Connecting a tool or turning it on for a project needs an active plan or trial. Otherwise Drobber says "Choose a plan under Billing to connect tools." On AppSumo Tier 1, task tools connected earlier stop sending and syncing. See Plans and prices.

Webhooks for your own code#

For a developer’s own system, a project’s Settings tab also has Webhooks & API: add a URL and Drobber posts a signed JSON payload to it when a comment is left, a reply is added or a comment is resolved. Zapier and Make don’t use these webhooks: they use a key instead, described in the API reference.