Basecamp, without opening Basecamp.
Put it on the to-do list, and mark it done when it is.
- Free to start
- No card
- Every write waits for you
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Basecamp details, and Ray takes it from there.
@Ray add that to the launch to-do list, due Friday.
@Ray what is still open on the launch to-do list?
@Ray tick the copy review off, Dana finished it.
@Ray comment on that to-do that we are waiting on legal.
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.
34 reads wired, 5 actions that wait for a human.
Runs on its own
What Ray reads in Basecamp
- To-dos, lists, card tables, and the projects around them
- Messages, documents, the schedule, and check-in answers
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Create a to-do with assignees and a due date
- Update a to-do, or complete and reopen one
- Comment on a to-do, message, or document
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 or trash anything
- Read the account's timesheet report
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Basecamp actions Ray can take, each one stopping in the thread with the real content before it happens.
- Complete Basecamp to-do
- Comment in Basecamp
- Create Basecamp to-do
- Reopen Basecamp to-do
- Update Basecamp to-do
Complete Basecamp to-do
Showing Todo id, each carrying the exact content that will land.
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
Ray uses Basecamp together with the rest of your tools.
One ask can read Basecamp, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
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.
Basecamp and Ray, answered
The questions teams ask before they connect Basecamp. Every answer is how this integration is built rather than a promise about it.
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.