Skip to main content
The Basecamp integration makes project conversations and to-dos available in your client work. Ask what is still open on an engagement, what the client posted on the message board this week, or what is on the schedule before the readout, and Hebno answers from Basecamp with each item cited. When a request implies a change, such as adding a to-do or posting a message, Hebno shows a confirmation card and writes to Basecamp only after you confirm.

​
At a glance

​
Before you start

You need:
  • A Basecamp account in the company account you want to use.
  • An allowed integration. An owner or admin sets Basecamp to Allow under Admin → Connectors → Catalogue.
Basecamp authorises apps through your 37signals ID, and its OAuth does not use scopes. Authorising Hebno grants access to the Basecamp accounts your 37signals ID can open, and Hebno then works with your own access in each project. Hebno uses these parts of the Basecamp API:

​
Connect Basecamp

1

Start the connection

Open Settings → Connections, find Basecamp and select Connect. You can also select Connect from the prompt in a chat.
2

Sign in with your 37signals ID

Sign in to Basecamp and select Yes, I’ll allow access.
3

Choose the account

If your ID opens more than one Basecamp account, choose the one Hebno should use. The card shows Connected with the account name.
Hebno reads and writes with your own permissions, so you see only the projects you have been added to in Basecamp. If you are a client in a project, you see only items that are visible to clients. Tokens are encrypted at rest. Select Disconnect at any time, or ask an admin to revoke the connection under Admin → Connectors → Connections.

​
What Hebno reads

Reads are live. Hebno queries Basecamp when a request needs it. Only what a reply used is stored with the conversation as its sources.
Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including messages and comments posted by clients in Basecamp.

​
What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Basecamp with editable fields

A Basecamp change pending confirmation. Nothing is written until you confirm.

In projects that include clients, the card shows whether the client can see a new to-do or message. Check the client visibility field before you confirm. Hebno never deletes or archives items or projects, changes who is on a project, or edits account settings. Writes are made as your Basecamp user, so Basecamp shows you as the author. Linking marks which Basecamp projects belong to an engagement, so you can ask “what is still open?” without naming the project.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Basecamp.
  3. Search by project name and select it. Repeat for each Basecamp project in the engagement.
In chats tagged to the project, Hebno starts with the linked Basecamp projects for any delivery question, and cards for new to-dos and messages default to them. See Linked records.

​
Use Basecamp in chat

  • Attach: open the + menu, choose Sources → Basecamp, and pick a project, a to-do list, a to-do, a message or a doc. Or type / and choose Basecamp.
  • Ask: name the project, to-do or person in your request. For example:
    List every open to-do on the Contoso pricing review, grouped by assignee, with anything past its due date first.
    Summarise what Contoso posted on the message board since 26 October and draft a reply for the team.
    Add a to-do to the Readout list to book the steering committee room, assign Priya Nair, due 10 November.
  • Research runs show a Checking Basecamp step, with a chip for each project, to-do and message it read.
  • Agents can read Basecamp on a schedule, for example a Monday digest of client messages and overdue to-dos. Writes an agent proposes appear in agent approvals for review.

​
Troubleshooting