Skip to main content
Connect Backlog by Nulab so CloudThinker agents can read your projects, issues, milestones, wikis, and pull requests, and create or update issues, milestones, and wiki pages when you ask. Backlog authenticates with an API key, and the key has the same project access as the Backlog user who issued it.

​
Prerequisites

  • A Backlog user who belongs to every project you want CloudThinker to read.
  • API access turned on for your space. If your space restricts it, a space administrator must enable it first.
  • Write permission on a project for that user, only if you want agents to create or update issues, milestones, or wiki pages there.
  • Permission to manage connections in your CloudThinker workspace. Backlog works on every CloudThinker plan.

​
Setup

1

Create an API key in Backlog

In Backlog, open your profile menu and go to Personal Settings → API. Enter a memo such as cloudthinker, register the key, and copy it.Issue the key from the user whose access you want CloudThinker to have. Anyone holding the key acts as that user.
2

Open Backlog in CloudThinker

In the sidebar, click More → Workspace settings → Connections. On the Builtin Connections tab, search for Backlog and click Connect.
3

Enter the domain and key

Fill in BACKLOG_DOMAIN with your full space host, such as myorg.backlog.com or myorg.backlog.jp. Paste the key into BACKLOG_API_KEY, then click Connect.Success state: CloudThinker tests the key and Backlog shows a Connected status.

​
Connection details

​
Required permissions

Backlog has no per-key scopes. The key can do whatever its user can do in Backlog. Reads run without asking. Writes go through Approvals: your Approval mode decides whether CloudThinker runs it, asks you first, or refuses it, and your Rules decide first once Rule enforcement is on for your workspace. In chat, CloudThinker only proposes a write when you name the item and the change. Resolve follow-up tickets are the exception: they run under the outcome you turn on in Resolve integrations.
Issue the key from a dedicated Backlog user that belongs only to the projects CloudThinker needs. Give it write permission only on projects where you want agents to file or update tickets. A dedicated user may count toward your Backlog plan’s user limit.

​
Agent capabilities

​
Verify the connection

You should get project names with keys like PLATFORM, and issue keys like PLATFORM-42 that you can open in Backlog.

​
Example prompts

The third prompt is a write, so CloudThinker shows the comment and sends it through your approvals before posting it.

​
Troubleshooting

The key is wrong, was deleted, or API access is off for the space. Create a new key under Personal Settings → API, confirm with a space administrator that API access is allowed, then update BACKLOG_API_KEY on the connection.
BACKLOG_DOMAIN holds only the space key (myorg) or the wrong region. Enter the full host exactly as it appears in your browser, such as myorg.backlog.com or myorg.backlog.jp, and reconnect.
The key’s user isn’t a member of those projects. Add the user to the project in Backlog, then ask CloudThinker to list your projects again.
The key’s user can read the project but can’t write to it. Give that user write permission on the project, or reissue the key from a user who has it, then approve the action again.
CloudThinker caps each Backlog response at about 10,000 tokens so replies stay readable. Narrow the request to one project, milestone, status, or assignee, or ask for a count first and then drill in.

​
Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • The key is the user. It carries every permission of the Backlog user who issued it, so issue it from a dedicated, least-privilege user and delete it in Backlog when you remove the connection.
  • Writes go through Approvals. Issue, wiki, and milestone changes go through Approvals, where your Approval mode settles each one. Choose Manual if a person should see every change, and give the key no more write access than those changes need.

Connections

Browse every service CloudThinker agents can use.

Resolve integrations

Turn on follow-up tickets in Backlog after an incident.