Fillin Forge connects with popular external services to help you automate your workflow. Instead of manually copying form data into your CRM, email list, or spreadsheet after every submission, integrations do it for you automatically. Every time someone submits a form, the data flows to the services you have connected — without any manual effort.
Integrations turn your forms from simple data collection tools into workflow automation hubs. A single form submission can simultaneously send you a Slack notification, add a contact to your CRM, subscribe the person to your email list, and log the data in a spreadsheet.
How Integrations Work
Every integration follows the same general pattern:
- You connect the service once in Fillin Forge > Settings (this is a one-time setup per service).
- You enable the integration on individual forms in the matching card of the form builder (for example Mailchimp or Google Sheets).
- Mailchimp and HubSpot need an email address: Fillin Forge uses the form’s first Email field, and the Mailchimp card also lets you choose which Email field to use.
- Every time someone submits the form, the data is automatically sent to the connected service.
Integration Overview
| Service | What it does | Free or PRO | Key storage |
|---|---|---|---|
| Slack | Posts a message to a Slack channel with submission data | PRO | WordPress |
| Discord | Posts a message to a Discord channel with submission data | PRO | WordPress |
| Telegram | Sends a message via Telegram bot with submission data | PRO | Forge API: the Chat ID is entered in WordPress, and each message goes through api.avakode.com (section 3.5 of the Privacy Policy) |
| Sends a template notification to the WhatsApp number saved in Settings | PRO | Forge API: the number is entered in WordPress and each message goes through api.avakode.com (section 3.5 of the Privacy Policy); the number stays linked to your site until the person sends STOP in the WhatsApp chat (section 7) | |
| Stripe | Accepts credit card payments within the form | PRO | WordPress |
| Google Maps / Yandex | Interactive map for address selection | Free | WordPress |
| Mailchimp | Subscribes the submitter to an email list | PRO | Forge API |
| Google Sheets | Adds a new row to a spreadsheet for each submission | PRO | Forge API |
| Google Calendar | Shows available time slots based on calendar availability | PRO | Forge API |
| HubSpot | Creates a contact (and optionally a deal) in your CRM | PRO | Forge API |
| Webhooks | Sends all form data as JSON to any URL you specify | Free | WordPress |
| PDF Receipts | Generates a formatted PDF of the submission | Free | None needed |
About Key Storage
Some integrations store credentials in WordPress and others on the Forge API server:
| Storage location | What it means | Used by |
|---|---|---|
| WordPress | Keys are in your WordPress database. You enter them directly in settings. | Stripe, Slack, Discord, Webhooks, Maps |
| Forge API | The OAuth tokens or API keys of Mailchimp, Google Sheets, Google Calendar and HubSpot are stored in our backend, not in your WordPress installation (section 3.5 of the Privacy Policy). For Telegram and WhatsApp the Chat ID or the number is entered in WordPress and each message is sent by your site to our API, api.avakode.com (section 3.5); the number stays linked to your site until the person sends STOP in the WhatsApp chat (section 7). | Mailchimp, Google Sheets, Google Calendar, HubSpot, Telegram, WhatsApp |
Where the Data Goes
Slack and Discord messages and webhooks are sent by your site directly to the address you saved. For Telegram, WhatsApp, Mailchimp, HubSpot, Google Sheets and Google Calendar, your site sends the submission data the integration needs to our API (api.avakode.com), and our API passes it on to the service. We relay this data and do not store its content. On a site with Fillin Forge Pro the same goes for the PDF of a single submission: its fields are sent to our API to build the file, and if our API cannot be reached the PDF is built on your site. The Privacy Policy lists what is sent for each integration.
Real-world example: You run an online coaching business. Your “Book a Discovery Call” form is connected to four services simultaneously: Google Calendar (to show available slots), Mailchimp (to add the person to your welcome email sequence), HubSpot (to create a CRM contact), and Slack (to notify your assistant). One form submission triggers all four actions automatically.> Tip: Only enable the integrations you actually need for each form. Each active integration adds a small amount of processing time to each form submission. A contact form does not need Google Sheets if you are already checking submissions in the dashboard.
> Good to know: Webhooks, the map field (Google Maps or Yandex) and the PDF of a submission are free. Every other integration in the table above needs a PRO license. On the free plan, you can use email notifications as your primary alert system, a webhook to send each submission to any URL, and CSV export to move data into external tools manually.
Common Mistakes to Avoid
- Connecting a service in Settings but forgetting to enable it on the specific form. Both steps are required.
- Not testing the integration after setup. Always submit a test entry and verify the data arrives in the external service.
- Mapping the wrong fields. Double-check that your form’s Email field is mapped to the integration’s Email property, not to the Name property.
[Screenshot: The integration cards of the form builder, each with its own toggle]
—