# Google Forms + Krokul CRM

Yes. Krokul CRM has a native Google Forms connector. A short Apps Script bound to your form sends each submitted response to Krokul, signed with your secret. Krokul finds the name, phone and email among the answers, opens a deal in the pipeline you chose and keeps the rest of the questionnaire on the deal as text.

**Status:** Native. **Automation platforms:** Zapier, Make, Albato.

## What your team gets

### A request form opens a deal with the full questionnaire

A visitor fills in your Google form with a name, a phone number and three questions about the project. The On form submit trigger runs the script, and Krokul gets every item response with its question title. Krokul creates or finds the contact, opens a deal named after the form and places the project answers in the request text as question and answer lines. The manager reads them on the deal.

### Questions with any wording map to the right fields

Your form asks "Where should we call you back?" instead of "Phone". In the connector settings you type that question title once, and Krokul takes the phone from it on every response. Without a setting, Krokul looks for familiar words in Ukrainian and English, then at the shape of the answer. An address with an @ becomes the email.

### A budget question sets the deal amount

A short answer such as "12 500 UAH" to the budget question becomes the expected amount of the deal. Krokul strips spaces and currency words and keeps the number. Pipeline reports count the deal at that size from the first day.

### A campaign tag travels in a prefilled link

Add a short question titled utm_source and share a prefilled link of the form for each campaign. Krokul reads utm_source, utm_medium and utm_campaign from such questions and stores them on the deal. The sources report then shows which campaign brought each form response.

## What moves between Google Forms and Krokul

| Google Forms | Krokul | Direction | When |
|---|---|---|---|
| FormResponse (On form submit) | Contact and a new deal in the chosen pipeline and source | Google Forms → Krokul | Each submitted response |
| Item responses for name, phone, email | Contact fields, matched to an existing contact | Google Forms → Krokul | Same response |
| Other item responses | Request text on the deal, one line per question | Google Forms → Krokul | Same response |
| Budget or amount answer | Expected amount of the deal | Google Forms → Krokul | When the question is answered |
| Questions titled utm_source, utm_medium, utm_campaign | UTM tags on the deal | Google Forms → Krokul | Response opened from a prefilled link |
| Response ID | External key that blocks a second deal | Google Forms → Krokul | Every delivery, including retries |
| Form title | Deal name | Google Forms → Krokul | Each submitted response |

## How to connect today

### Native connector in the Marketplace

1. In the Krokul Marketplace, open Google Forms and press Connect. Pick the pipeline, the source and the responsible person, set a shared secret and copy the flow address.
2. Open your form in Google Forms, open the Apps Script editor from the form menu and paste the script shown on the connector page with your address and secret.
3. In Apps Script, add a trigger for the onKrokulSubmit function with the event source From form and the event type On form submit.
4. Optionally type the exact titles of the name, phone, email, comment and amount questions in the connector settings.
5. Submit a test response. The integration journal shows the response, the contact and the deal it opened, or the reason it was rejected.

### Krokul app in Zapier, Make or Albato

1. Connect the Krokul app with an API key.
2. Start from the Google Forms trigger New Form Response in Zapier, Watch Responses in Make or Answer by form created in Albato, and finish with the Krokul action Create Deal or Create Task.

**Triggers:** New Form Response; New or Updated Form Response.

### For integrators

Google Forms has no outgoing webhook, so the Apps Script trigger is the sender. It runs in the Google account of the form owner and needs no Google permissions in Krokul. Krokul checks the signature header, a HMAC-SHA256 of the raw body in hex or base64. Unsigned requests get a 401. For your own flows there is the Krokul REST API, signed outgoing webhooks such as card.created, external keys and a sandbox company.

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

## Questions and answers

### Does Krokul need access to my Google account for Google Forms?

No. The script lives in your form and sends responses out. Krokul only receives them at the flow address and checks the signature.

### What happens to answers Krokul cannot map?

They stay on the deal. Every answer that did not become a contact field goes into the request text as a line with the question title and the answer.

### Can one Google Forms response create two deals?

No. The script sends the response ID, and Krokul uses it as an external key. A repeated delivery of the same response finds the first deal.

### Can I connect several forms?

Yes. Each form gets its own flow in the Marketplace with its own pipeline, source and question mapping.

## Limits

The form, its questions and the response summary stay in Google Forms, together with any linked spreadsheet. Krokul receives responses submitted after the script trigger is added and writes nothing back to the form.

## Related services

- [Typeform](https://krokul.com/en/integrations/typeform/index.md)
- [Jotform](https://krokul.com/en/integrations/jotform/index.md)
- [WordPress forms](https://krokul.com/en/integrations/wordpress-forms/index.md)
- [Webflow](https://krokul.com/en/integrations/webflow/index.md)
- [Google Sheets](https://krokul.com/en/integrations/google-sheets/index.md)
- [Google Ads](https://krokul.com/en/integrations/google-ads/index.md)

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

Google Forms is a trademark of Google LLC. Krokul is not affiliated with Google.

Updated: 2026-10-15

---

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