# Basecamp + Krokul CRM

Yes. Krokul CRM integrates with Basecamp. A won deal opens a Basecamp project from your template with the client contact invited, Krokul tasks for delivery appear as Basecamp to-dos, and completed to-dos, comments and uploads come back to the deal. The Krokul app in Zapier or Make runs these flows, and the Krokul API with webhooks covers custom ones.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make.

## What your team gets

### A won deal opens a ready project

When a deal reaches a won stage, the connector builds a Basecamp project from your onboarding template, so the to-do lists, message board and schedule are there from the first day. The project takes the deal name, and its description carries the client company, the amount and the manager. Krokul links its own project for the deal to the Basecamp project ID.

### The client contact joins the project

The contact on the deal is added to the Basecamp project with their name and email. Basecamp invites them as a client, and they see what your team makes visible to clients. The account manager skips the invitation step.

### Tasks and to-dos close each other

A delivery task created in Krokul becomes a Basecamp to-do in the list you chose, with the assignee and due date. Basecamp sends todo_completed when someone ticks it off, and the Krokul task moves to done. Reopening it sends todo_uncompleted, and the task opens again.

### Comments and uploads reach the deal feed

comment_created on a linked to-do or message posts the comment to the deal feed with its author. A new upload in the project appears on the deal as a file link. The account manager follows the work without logging in to Basecamp.

## What moves between Basecamp and Krokul

| Basecamp | Krokul | Direction | When |
|---|---|---|---|
| Project from a template | Won deal and its Krokul project | Krokul → Basecamp | A deal reaches a won stage |
| Person on the project (client) | Contact on the deal | Krokul → Basecamp | The project is created |
| To-do | Task | Krokul → Basecamp | A delivery task is created in Krokul |
| todo_completed, todo_uncompleted | Task status | Basecamp → Krokul | Someone ticks or reopens the to-do |
| comment_created | Comment in the deal feed | Basecamp → Krokul | A comment is posted on a linked recording |
| Upload | File link on the deal | Basecamp → Krokul | A file is uploaded to the project |
| Message | Deal stage change | Krokul → Basecamp | The deal moves to a stage you mark for updates |

## How to connect today

### Krokul app in Zapier or Make

1. Connect the Krokul app with a Krokul API key and Basecamp with your Basecamp login.
2. Use the Krokul trigger Deal Won with the Basecamp action Create Project From Template in Zapier or Create a Project Construction in Make, then Add Person to a Project for the deal contact.
3. Pair the Krokul trigger for new tasks with Create To-Do, and run the Basecamp trigger To-Do Completed/Uncompleted into the Krokul action Update Task Status.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with scopes for deals, projects, tasks and activities.
2. Subscribe to card.won and task.created with webhook/api-upsert and verify x-crm-signature. On card.won, create the Basecamp project from the template and the Krokul project with project/api-createFromCard.
3. Store each Basecamp project ID and to-do ID on the Krokul record with externalRef/api-upsert.
4. Add a Basecamp webhook for the Todo and Comment types, resolve the recording through externalRef/api-resolve, and call task/api-updateStatus or activity/api-create.

**Triggers:** New Project; New To-Do; To-Do Completed/Uncompleted; New Comment; New Upload; New Message; Watch To-Dos; Watch Comments.

**Actions:** Create Project From Template; Create To-Do; Create To-Do List; Update To-Do; Add Person to a Project; Create Message; Create Comment on Todo; Find Project; Find To-Do; Create a Project Construction; Complete a To-Do.

### For integrators

The Basecamp API uses OAuth 2 and requires a User-Agent with the app name and a contact. Rate limits answer 429 with Retry-After. Webhooks go to HTTPS addresses only, can be limited to recording types such as Todo and Comment, and are retried up to ten times before Basecamp turns them off. Krokul keeps Basecamp IDs as external keys, signs its own webhooks and logs every delivery.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Basecamp?

Yes. Krokul integrates with Basecamp through the Krokul app in Zapier and Make, and through its API and webhooks.

### Can a won deal create a Basecamp project from a template?

Yes. The Krokul trigger Deal Won starts a project from your Basecamp template, named after the deal, with the client contact added as a person on it.

### Which Basecamp event closes a Krokul task?

todo_completed. Basecamp sends it when a linked to-do is ticked off, and todo_uncompleted reopens the Krokul task.

### Do Basecamp comments show up in Krokul?

Yes. Comments on linked to-dos and messages arrive with comment_created and appear in the deal feed with the author name.

## Limits

Message boards, to-do lists, schedules, Campfire chats and client access are managed in Basecamp. Krokul holds the sale, the client company, the hours budget and the documents that bill the work.

## Related services

- [Asana](https://krokul.com/en/integrations/asana/index.md)
- [Trello](https://krokul.com/en/integrations/trello/index.md)
- [ClickUp](https://krokul.com/en/integrations/clickup/index.md)
- [Jira](https://krokul.com/en/integrations/jira/index.md)
- [Notion](https://krokul.com/en/integrations/notion/index.md)
- [Slack](https://krokul.com/en/integrations/slack/index.md)

[Projects and tasks](https://krokul.com/en/integrations/category/project-management/index.md)

Basecamp is a trademark of 37signals LLC. Krokul is not affiliated with Basecamp.

Updated: 2026-10-15

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs