# Asana + Krokul CRM

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

## What your team gets

### Every new client gets the same onboarding plan

A deal moves to a won stage, and the connector creates a Project in Asana from your onboarding template. The project is named after the deal, and its notes carry the client company, the contact and the amount. Delivery opens a ready plan with the usual sections instead of copying tasks by hand.

### One sale, two projects with different jobs

For hour packages, Krokul also creates its own project from the deal, with the client, manager, amount and line items. Asana keeps the task plan, and Krokul keeps the hours budget. Krokul stores the Asana ID on its own record, so each side opens the other in one click.

### Completing a task closes it on both sides

An account manager asks delivery for a document through a Krokul task, and the connector creates its twin in Asana. Marking it complete in Asana sets the Krokul status to `done`. Closing it in Krokul completes the Asana copy, so nobody chases finished work.

### Tracked time fills the hours package

A Time Tracking Entry on a linked task becomes a row of hours on the Krokul project, with the date and the person. When the entry changes or is removed in Asana, the row follows. At month end Krokul drafts the act of work from those hours and shows any overage on its own line.

### Milestones become notes on the deal

When a task moves between sections, for example from Build to Review, the connector adds a short note to the deal feed. Comments marked for the client in Asana reach the same feed. The account manager follows progress without an Asana seat.

## What moves between Asana and Krokul

| Asana | Krokul | Direction | When |
|---|---|---|---|
| Project (from template) | Won deal | Krokul → Asana | A deal reaches a won stage |
| Project ID | Krokul project with hours budget | Asana → Krokul | The Asana project is created |
| Task | Task | Krokul ↔ Asana | A delivery task is created or completed in either system |
| Time Tracking Entry | Hours on the project | Asana → Krokul | An entry is added, changed or removed |
| Section change | Note in the deal feed | Asana → Krokul | A linked task moves to another section |
| Story (comment) | Comment in the deal feed | Asana → Krokul | A comment passes the connector filter |

## How to connect today

### Krokul app in Zapier, Make, n8n or Albato

1. Add the Krokul app and connect it with an API key.
2. Use the Krokul trigger Deal Won with the Asana action Create Project From Template, and Task Created with the Asana action Create Task.
3. For the way back, start from the Asana trigger Completed Task or Task Moved to Section and run a Krokul action such as Update Task or Create Comment.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with scopes for deals, projects, tasks and activities.
2. Subscribe a webhook to card.won and task.created, and verify each delivery by its x-crm-signature header. On card.won, create the Asana project and the Krokul project with project/api-createFromCard.
3. Keep each Asana task gid on its Krokul task through externalRef/api-upsert.
4. From Asana webhooks, close the Krokul task with task/api-updateStatus and record tracked time with project/api-logHours.

**Triggers:** New Task; Completed Task; Updated Task; Task Moved to Section; New Comment on a Task; New Project.

**Actions:** Create Project From Template; Create Project; Create Task; Update Task; Create Comment/Story; Find or Create Task.

### For integrators

Asana webhooks report added, changed, removed, deleted and undeleted events on tasks, projects, sections, stories and time tracking entries. A custom service needs no polling. It can resolve the Asana task through Krokul external keys, then write with the public REST API. Krokul signs its own webhooks, keeps a delivery log, and answers rate limits with 429 and Retry-After. A sandbox company with an API key is there for tests.

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

## Questions and answers

### Is there an Asana integration for Krokul CRM?

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

### Can a won deal start an Asana project from a template?

Yes. The Krokul trigger Deal Won runs the Asana action Create Project From Template, and the project takes the name of the deal.

### Which task changes go both ways?

Creation and completion. A delivery task created in Krokul appears in Asana, and completing it on either side closes it on the other. Due dates follow the Krokul task.

### Can time tracked in Asana count against an hours package?

Yes. Each time tracking entry becomes hours on the linked Krokul project, and edits in Asana update the same row.

## Limits

Task plans, sections, dependencies and timelines stay in Asana. Krokul holds the client, the deal, the sold hours and the documents that bill them.

## Related services

- [Jira](https://krokul.com/en/integrations/jira/index.md)
- [ClickUp](https://krokul.com/en/integrations/clickup/index.md)
- [Trello](https://krokul.com/en/integrations/trello/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)

Asana is a trademark of Asana, Inc. Krokul is not affiliated with Asana.

Updated: 2026-10-12

---

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