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.
Automation platformsZapierMaken8nAlbato
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.
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.
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.
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.
| Tally | Direction | Krokul | When |
|---|---|---|---|
| FORM_RESPONSE: INPUT_EMAIL, INPUT_PHONE_NUMBER | Tally → Krokul | Contact, matched by email or phone | Each submission |
| Company answer (INPUT_TEXT) | Tally → Krokul | Client company linked to the contact | Same submission |
| Form (formId, formName) | Tally → Krokul | Deal in the pipeline set for the form, source | Each submission |
| CALCULATED_FIELDS | Tally → Krokul | Expected deal amount | Same submission |
| DROPDOWN, MULTIPLE_CHOICE, CHECKBOXES | Tally → Krokul | Custom deal fields | Same submission, by the field mapping |
| HIDDEN_FIELDS | Tally → Krokul | UTM tags and partner code on the deal | Same submission |
| FILE_UPLOAD, TEXTAREA | Tally → Krokul | File link and first message on the deal | Same submission |
Yes. Krokul integrates with Tally through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.
No. Krokul maps each Tally field by its key, which stays the same when you edit the question label.
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.
No. Tally documents webhooks as available to all users at no cost.
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.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Tally is a trademark of Tally BV. Krokul is not affiliated with Tally.