# Tally + Krokul CRM

Yes. Krokul CRM integrates with Tally. When someone submits a Tally form, Krokul receives the FORM_RESPONSE event and creates or updates the contact, links the client company and opens a deal in the pipeline set for that form. Hidden fields, calculated totals and uploaded files go to the deal as well. Teams connect it through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.

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

## What your team gets

### A request for a quote opens a deal

A procurement manager fills in your Tally form "Request a quote" with name, work email, phone and company. Tally posts FORM_RESPONSE, and Krokul reads data.fields by each field key, the stable ID that survives a renamed question. INPUT_EMAIL and INPUT_PHONE_NUMBER find or create the contact. The company answer links the client company, and the deal opens with the form name as its source.

### A calculated total becomes the expected amount

Tally forms can compute a price from the chosen options, for example seats times a plan rate. Krokul takes that CALCULATED_FIELDS value as the expected amount of the deal. DROPDOWN and MULTIPLE_CHOICE answers, such as the product line or the delivery region, fill custom deal fields. The manager opens a priced deal.

### Campaign tags travel in hidden fields

The link to the form carries utm_source, utm_campaign or a partner code as Tally hidden fields. They arrive as one HIDDEN_FIELDS entry in the submission, and Krokul writes each value to the deal. The sources report then counts deals for every campaign and partner.

### Attached specifications stay with the deal

A buyer uploads a technical specification through a FILE_UPLOAD question. Krokul adds the file link to the deal files, and long TEXTAREA answers become the first incoming message in the deal feed. The engineer who prepares the offer opens one deal and sees the whole request.

## What moves between Tally and Krokul

| Tally | Krokul | Direction | When |
|---|---|---|---|
| FORM_RESPONSE: INPUT_EMAIL, INPUT_PHONE_NUMBER | Contact, matched by email or phone | Tally → Krokul | Each submission |
| Company answer (INPUT_TEXT) | Client company linked to the contact | Tally → Krokul | Same submission |
| Form (formId, formName) | Deal in the pipeline set for the form, source | Tally → Krokul | Each submission |
| CALCULATED_FIELDS | Expected deal amount | Tally → Krokul | Same submission |
| DROPDOWN, MULTIPLE_CHOICE, CHECKBOXES | Custom deal fields | Tally → Krokul | Same submission, by the field mapping |
| HIDDEN_FIELDS | UTM tags and partner code on the deal | Tally → Krokul | Same submission |
| FILE_UPLOAD, TEXTAREA | File link and first message on the deal | Tally → Krokul | Same submission |

## How to connect today

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

1. Connect the Krokul app with a Krokul API key and connect your Tally account or form webhook on the platform.
2. Start from New Submission in Zapier, Watch New Responses in Make or the Tally Trigger node in n8n, and add the Krokul actions Find Contact and Create Deal.
3. Use the Krokul trigger Deal Created to post the new request to the team chat or start a reply email.

### Custom flow through the Krokul API and webhooks

1. Make a Krokul API key with scopes for contacts, client companies and deals.
2. In the form, open Integrations and connect a webhook to your handler with a signing secret, or create it with POST /webhooks in the Tally API.
3. Check the Tally-Signature header, read data.fields by key, call contact/api-find and then contact/api-create, clientCompany/api-create and card/api-create for whatever is missing.
4. Store the Tally submissionId on the deal with externalRef/api-upsert, so a retried delivery updates the same deal.

**Triggers:** New Submission; Watch New Responses.

**Actions:** List Fields Definitions.

### For integrators

Tally signs each delivery with a Tally-Signature header, a base64 HMAC-SHA256 of the raw body with your signing secret. Your endpoint must answer with a 2XX status within 10 seconds, and Tally retries a failed delivery five times, the last one a day later. A forged request fails the check. Webhooks are available on every Tally plan, and past submissions can be read with GET /forms/{formId}/submissions. On the Krokul side, contact/api-find avoids duplicates, externalRef keeps the submission ID, and a sandbox company accepts test submissions.

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

## Questions and answers

### Does Krokul integrate with Tally?

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

### Will renaming a question in Tally break the mapping?

No. Krokul maps each Tally field by its key, which stays the same when you edit the question label.

### Can Krokul load submissions sent before the connection?

Yes. Krokul reads earlier submissions of the form through the Tally API and creates the missing contacts and deals once, skipping submissions it already has.

### Do Tally webhooks need a paid plan?

No. Tally documents webhooks as available to all users at no cost.

## Limits

Form building, conditional logic, payments collected in the form and the response table stay in Tally. The Tally API accepts 100 requests per minute, and webhook deliveries do not count toward that limit.

## Related services

- [Typeform](https://krokul.com/en/integrations/typeform/index.md)
- [Jotform](https://krokul.com/en/integrations/jotform/index.md)
- [Google Forms](https://krokul.com/en/integrations/google-forms/index.md)
- [WordPress forms](https://krokul.com/en/integrations/wordpress-forms/index.md)
- [Webflow](https://krokul.com/en/integrations/webflow/index.md)
- [Eventbrite](https://krokul.com/en/integrations/eventbrite/index.md)

[Forms and ad inquiries](https://krokul.com/en/integrations/category/lead-capture/index.md)

Tally is a trademark of Tally BV. Krokul is not affiliated with Tally.

Updated: 2026-10-15

---

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