Integration · Automate and collaborate
Basecamp and Meteor AI agents
Connect Basecamp to a WhatsApp Met: check projects, create to-dos with an owner and due date, comment and recap the team's week.
How do I connect Basecamp to WhatsApp to follow projects without opening it?
With the Basecamp ready connector, your Met works in your Basecamp account with the permissions of the person who authorizes the connection. It finds a project, reads its recent activity, messages, to-dos and cards, and tells you what is overdue, what has no owner and what is coming up on the schedule. If the connection has full access, it also creates to-do lists and to-dos with an owner and a due date, cards, documents and comments with mentions. That way, what a customer asks for on WhatsApp ends up assigned in the project, and you get the weekly recap without opening Basecamp. The official server is included with every Basecamp account.
What it automates
What a Meteor Met does with Basecamp
Assign in the project what the customer asks for on WhatsApp
When a customer asks for a change or a deliverable, the Met finds their project, checks who is on it and creates the to-do in the right list, with an owner and a due date. The request no longer stays in someone's chat.
Tell the customer where their project stands
The Met reads the project's recent activity and its open to-dos and replies on WhatsApp with what is done and what is left. The activity it reads goes back to the project's latest 100 events.
Get the weekly recap without opening Basecamp
A scheduled task asks the Met for the recap of the last days, the overdue or unassigned to-dos across all projects and what is coming up on the schedule, and sends it to you on WhatsApp with a link to each item.
Alert the team with a comment and a mention
If a customer reports something urgent, the Met leaves a comment on the to-do or the project message and mentions the person in charge, who gets the alert in Basecamp.
35 tools
Everything your Met can ask Basecamp for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
get_me | Returns the person who authorized the connection and the Basecamp account it works in. |
get_basecamp_guide | Returns the server's reference notes on how Basecamp works, in general or by topic. |
get_by_url | Opens a Basecamp link and returns the record, its IDs and where a reply goes. |
search | Searches by keyword across everything the connected account can see. |
list_projects | Lists the projects in the connected Basecamp account. |
get_project | Opens a project and returns its tools, with the ID each one uses. |
create_project | Creates a new project in the Basecamp account. |
list_project_people | Lists the people on a project, to assign them work or mention them. |
list_pingable_people | Lists the people who can be mentioned in a comment. |
get_project_timeline | Shows a project's recent activity, up to its latest 100 events. |
get_my_assignments | Lists the work assigned to the connected person, priorities first. |
get_my_completed_assignments | Lists the connected person's finished assignments, without completion dates. |
get_my_day | Shows today's schedule and the to-dos due today for the connected person. |
get_overdue_todos | Lists the connected person's overdue to-dos. |
get_upcoming_schedule | Shows the events in a date range across the account, including recurrences. |
list_schedule_entries | Lists a schedule's events; a recurring series appears only once. |
get_my_notifications | Brings the connected person's notifications, unread first. |
get_catchup | Recaps what happened over the last days, up to 14, with announcements, to-dos and activity by project. |
list_messages | Lists the messages on a project's message board. |
create_comment | Leaves a comment on a record and can mention people on the team. |
create_document | Creates a document in a project's Docs & Files, as a draft or published. |
list_todolists | Lists a project's to-do lists. |
list_todos | Lists the to-dos in a to-do list. |
get_todo | Opens a to-do and returns its Basecamp link. |
create_todolist | Creates a to-do list inside a project. |
create_todo | Creates a to-do with owners and a due date, and notifies only when asked to. |
list_everything_todos | Lists to-dos across all projects by state, for example overdue or unassigned. |
list_everything_cards | Lists cards across all projects by state, for example overdue. |
get_card_table | Shows a Card Table with its columns. |
create_card | Creates a card in a Card Table column. |
update_card | Updates a card, for example to change its owners. |
get_questionnaire | Opens a project's automatic check-ins. |
list_questions | Lists the questions of a project's automatic check-ins. |
get_answers_by_person | Brings one person's answers to a check-in question. |
create_answer | Posts an answer to an automatic check-in question. |
The limits
What the Basecamp integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not ask for confirmation in the chat before writing to Basecamp. Control sits in two places: the access approved when connecting (read-only or full) and the actions the admin leaves on in Connections.
-
It sees no more than the person who authorized the connection. If that person is not on a project, the Met cannot see it either, and it works in one Basecamp account per connection.
-
It does not read further back than the server returns: a project's activity goes back to its latest 100 events and the recap of what happened covers 14 days at most.
-
This page does not include the complete, move or trash actions. The server has them, but their exact names are not published in any official source. The trash actions start switched off: the admin decides in Connections whether to turn them on.
-
It does not notify anyone on its own: a to-do or an event notifies only when asked to, and a message or document created as a draft reaches no one until it is published.
Before you start
What you need to connect Basecamp
- 1
A Basecamp account with access to the projects
The official server is included with every Basecamp account at no extra cost. Connect with a person who is on the projects the Met will use, because it works with their permissions.
- 2
Connect it in Met
In Met, open Connections → Basecamp → Connect. A Basecamp window opens so you can sign in, pick the account and approve access: read-only or full access. Then you choose which actions stay on.
Frequently asked questions
Questions about Basecamp and Meteor
No. It works as the person who authorized the connection: if that person cannot see a project, a message or a file in Basecamp, neither can the Met.
Yes. When you approve the connection you choose read-only access, and with it the Met can search and read but cannot create or change anything in Basecamp.
No. Basecamp says its server is included with every account. What you pay is your Basecamp plan; Meteor does not resell Basecamp.
The one you pick when you approve access. To switch, disconnect and connect again choosing the other account.
Step by step
Automations that use Basecamp
Complete tasks, with the steps and the tools that run at each one.
Automate and collaborate
Other integrations in the same family
Want to see a Met running Basecamp?
We will show you with your own account connected, not with a canned demo.