How to Connect Gravity Forms to CiviCRM (Donations, Volunteers, Events)

If your charity, association or campaign runs CiviCRM, every form on your website is a doorway into it: donation forms, volunteer sign-ups, newsletter forms, event registrations, membership enquiries. Yet on many WordPress sites those forms still end in an e-mail inbox, and somebody copies names, addresses and amounts into CiviCRM by hand. This guide explains why that happens, what the usual workarounds cost, and how to connect Gravity Forms to CiviCRM directly, on the same site or over the CiviCRM API, with the Gravity Forms CiviCRM Add-On.

The problem: your forms and your supporter database do not talk

CiviCRM is built for organisations that live on relationships: donors, members, volunteers, event participants. It keeps one record per person with every gift, every event and every conversation. Gravity Forms is the form builder many of those same organisations use on their WordPress website, because it is flexible, handles payments and conditional logic, and does not need a developer for every new form.

The gap sits between the two. A supporter fills in the donation form; Gravity Forms stores the entry and sends a notification. Then a staff member or a volunteer opens CiviCRM, searches for the person, wonders whether “Maren Okafor” and “M. Okafor” are the same supporter, types in the new address, records the gift with the right financial type, adds the person to the newsletter group and maybe writes a note about what they ticked on the form. Multiply that by every form, every week.

Manual copying has three costs. It takes time that a small team does not have. It creates mistakes: wrong amounts, missed Gift Aid declarations, duplicates when the same person is entered twice. And it delays everything that depends on CiviCRM, like the thank-you letter, the receipt, the volunteer rota and the next mailing, because the data is only as fresh as the last copy session.

CiviCRM has its own contribution and event pages, but many organisations prefer their Gravity Forms: the forms match the website, they already connect to payment gateways, they use conditional logic and multi-page layouts, and the web team knows how to build them. Throwing those forms away to use a different form system is rarely what anyone wants.

Why webhooks, automation services and custom code fall short

There are three common ways to bridge the gap, and each has a price.

Automation services. A service such as Zapier or Make can catch a form entry and push it to CiviCRM. That means a monthly subscription that grows with the number of tasks, your supporters’ personal data passing through another company’s servers, and an automation chain that someone has to rebuild whenever a field changes. Matching existing contacts, adding groups and tags, and keeping a donation Pending until the payment clears quickly turns into a long, fragile chain of steps.

Webhooks plus CiviCRM extensions. Another route is to send each entry as a webhook and configure a matching processor inside CiviCRM. It works, but it needs the webhooks feature of the most expensive Gravity Forms licence, an extension installed and configured on the CiviCRM side, and someone who understands both systems to maintain the mapping. Every new form becomes a small integration project.

Custom development. A developer can write code that calls the CiviCRM API on submission. For a single form that is fine; for a dozen forms, with payments, duplicates, retries when CiviCRM is busy, and updates to WordPress, Gravity Forms and CiviCRM every few months, it becomes code that someone has to own for years.

Step-by-step: connect Gravity Forms to CiviCRM

Step 1: install the add-on and choose where CiviCRM is

Install the add-on, then go to Forms → Settings → CiviCRM and activate your licence. Under Where is CiviCRM? pick On this WordPress site if the CiviCRM plugin runs on the same WordPress site. That is all: the add-on talks to CiviCRM directly on the server, with no API key.

If CiviCRM runs on another website, pick Another CiviCRM site (API). Enter the site address, choose the address style (Clean URLs, WordPress, Joomla or a custom template), and paste the API key of a dedicated CiviCRM API user. Add the site key if your CiviCRM asks for one. Save and press Test connection: the add-on reads one contact and your lists, and writes nothing.

Step 2: create a feed and map the supporter

Open the donation form, go to Settings → CiviCRM and add a feed. Pick the contact type, Individual for most forms, Organization for corporate partners, Household if you work with households, and map the form fields: name, e-mail, phone and each part of the address. The location type (Home, Work) and phone type (Mobile, Phone) come from your CiviCRM. Then map your CiviCRM custom fields, such as a preferred contact method, interests or a Gift Aid declaration; the list is read from your CiviCRM, so new custom fields appear without any code.

Under Matching existing contacts, choose how returning supporters are found: by the same e-mail address, by your CiviCRM unsupervised duplicate rule, or by any other dedupe rule you set up in CiviCRM. Choose whether a returning supporter’s empty fields are filled, or all mapped fields are updated.

Step 3: groups, tags and a record of the submission

Tick the groups the supporter should join, such as your newsletter list or a volunteers group, and the tags you use to segment, like Website. Tick Record an activity to keep the full form answers on the contact’s record, with a subject such as Donation form: {form_title}. Choose Scheduled as the status when a staff member should follow up.

Step 4: record the donation the right way

Tick Record a contribution, choose the amount field, the financial type (Donation, Member Dues, Event Fee) and the payment method. This is where a plain integration usually goes wrong: a donation must not show as received before the money has arrived. The add-on records the contribution as Completed only when the Gravity Forms payment status is Paid. While a card payment is still processing, the contribution is Pending, and it moves to Completed when the payment add-on reports the payment, or to Refunded, Failed or Cancelled. Offline gifts such as cheques and pledges are recorded as Pending for your finance team.

Submit a test entry. The entry gets a note with the CiviCRM contact id, a link to the contact and a line for each step, and a CiviCRM box on the entry screen.

In CiviCRM you see the supporter with the e-mail, phone, address and custom fields, the group, the tag, the activity and the contribution.

Pro tips for real organisations

• Volunteer and event forms: add a second form with Register the contact for a CiviCRM event, pick the event and the participant role (for example Volunteer). Use conditional logic to register only people who chose a certain shift.
• Supporter number in the thank-you message: put {civicrm_contact_id} in the confirmation or the notification, so supporters can quote it when they call.
• One form, several feeds: one feed adds everyone to the newsletter group; a second, conditional feed records gifts over a certain amount with a Major donor tag and a scheduled follow-up activity.
• Busy CiviCRM servers: if CiviCRM is down for maintenance, the add-on tries again after 5 minutes, 30 minutes and 2 hours. Resending an entry never records a second gift or activity.
• Keys out of the database: set the API key and site key in wp-config.php with GECIVI_API_KEY and GECIVI_SITE_KEY.

Frequently asked questions

CiviCRM is a registered trademark of CIVICRM LLC. The Gravity Forms CiviCRM Add-On is made by GravityExtra and is not affiliated with or endorsed by CIVICRM LLC.