Basecamp, without opening Basecamp.
Put it on the to-do list, and mark it done when it is.
In your channel
Ask Ray for something in Basecamp and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in Basecamp
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Basecamp
- List project people
- Get buckets card tables lists cards
- Get buckets message boards messages
- Get buckets questionnaires
- Get buckets questionnaires questions
- Get buckets question answers
- Get buckets recordings events
- Get buckets schedules entries
- Get buckets todolists todos
- Get buckets todos
- Get buckets todosets todolists
- Get buckets vaults
- Get buckets vaults documents
- Get card
- Get card table
- Get card table column
- Get comment
- Get document
- Get message
- Get message board
- Get my profile
- Get people
- Get people by person id
- Get project
- Get projects
- Get projects people
- Get projects recordings
- Get schedule
- Get schedule entry
- Get todo
- Get todolist
- Get todoset
- List comments
- List todolists
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Complete Basecamp to-do
- Comment in Basecamp
- Create Basecamp to-do
- Reopen Basecamp to-do
- Update Basecamp to-do
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete buckets card tables columns on hold
- Validate credential
- Delete buckets recordings pin
- Delete campfire line
How Ray works with Basecamp
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Basecamp
One click, right where you asked. Ray posts a connect card, you authorise Basecamp with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Basecamp, and tell Dana it is being looked at.
Complete Basecamp to-do
- Waiting on
- your approval
What does connecting Basecamp to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Basecamp and it can do the Basecamp part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Basecamp account, so Ray can only reach what that person can already reach, and the history in Basecamp shows who actually asked.
Security and permissions
- You authorise Basecamp on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Basecamp in a message, or uninstall Ray and every connection it held is revoked.
More issue tracking integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Basecamp.
Free to start, no credit card, and it asks before it acts.