GC API Alchemist 1.0.22

GC API Alchemist connects Gravity Forms to any REST API with no-code feeds. Send entries with GET, POST, PUT, PATCH, or DELETE, capture responses on submission, and prefill fields with live data through Populate Anything. Simple on WordPress.

VERSION:
1.0.22
UPDATED:
2026-11-20
DEVELOPER:
Gravity Wiz
LICENSE:
GPLv2 or greater
AUTO UPDATE:
Yes

Description

Who This Is Built For

Gravity Forms administrators who keep running into the same wall will get the most out of GC API Alchemist: the form works, the entry is saved, and then somebody has to copy the data into another system by hand. Agency developers, operations managers, and WordPress site owners who maintain lead capture, intake, order, or booking forms all hit this sooner or later. GC API Alchemist is a feed-based add-on that moves that data to an external REST API, and it can pull data back the other way.

Consider a marketing lead who needs every qualified submission pushed into a CRM, with a Slack alert on top. Or a logistics coordinator who wants a delivery address sent to a shipping service the moment a customer submits. Or a developer who builds client sites and is tired of writing custom PHP hooks for each new webhook request. The interface is built around feeds rather than code, so these jobs become configuration tasks instead of development projects.

It also suits people who already use Populate Anything. If your forms need dropdowns, choices, or field values that reflect live information from an outside service, the plugin’s API connections can supply that data before the visitor ever sees the form.

What GC API Alchemist Does

The GC API Alchemist WordPress plugin turns Gravity Forms into a client for any REST API. You create a feed on a form, point it at an endpoint, and decide what gets sent and when. Requests can use GET, POST, PUT, PATCH, or DELETE, which covers creating records, updating them, and removing them. You control parameters, headers, body content, and formatting, so the request matches what the receiving service expects.

Data travels in both directions. On submission, a feed can capture the API’s response and store it with the entry. That response can then feed entries, confirmations, notifications, and conditional logic. Before submission, connections made through the plugin can be used with Populate Anything to fill fields and choices with live API data.

How are responses handled when an API is slow?

Feeds run asynchronously by default, so a sluggish external service does not hold up the person filling in your form. When you capture a response, there are two paths. The plugin can process the response right after submission, or it can generate a callback URL in advance and update the matching entry whenever the API finally answers. The second path suits processes that take time, such as document generation, background verification, or any service that replies minutes later.

If a form genuinely needs the answer before it can finish, there is an option to require the response to complete the submission. It is available in Simple Response Mode, and it is the one exception to the asynchronous default.

What are API Connection Profiles?

A profile stores the settings you would otherwise retype for every feed: base URL, authentication, headers, and schema. Build it once, then reuse it across as many feeds and forms as you like. When a key rotates or a base URL changes, you update the profile rather than hunting through a dozen feeds. The same profiles can power dynamic field population when paired with Populate Anything.

Key Capabilities

  • All common HTTP methods: send GET, POST, PUT, PATCH, and DELETE requests from a Gravity Forms feed, with control over payload, headers, and request conditions.
  • Response capture: store what the API returns and reuse it in entries, confirmations, notifications, and conditional logic.
  • Callback URLs: handle instant or delayed workflows by letting the remote service update the entry when it finishes.
  • API schema mapping: load a schema to discover endpoints, validate parameters, and map form data accurately without flipping between browser tabs and documentation.
  • API Connection Profiles: centralize base URL, authentication, headers, and schema for reuse across forms.
  • Populate Anything integration: fill fields and dynamic choices with live API data before submission.
  • Conditional triggers: fire webhooks based on conditional logic or on payment processing events.
  • Retry from entries: rerun a failed feed as many times as needed from the entry screen, or in bulk with Feed Forge.
  • Entry-level record keeping: Gravity Forms retains a record of your data, so you can inspect what was sent.
  • Built on the Gravity Connect framework: your data goes from your site to the endpoint you choose, and does not pass through the vendor’s servers.

Which workflows can you automate?

Because it speaks plain REST, the range is wide. You can trigger custom workflows in n8n, Trello, or Zapier, or call your own site’s WordPress REST API to take actions on it. You can connect forms to services such as Google Workspace, WSDesk, or WebMerge, and post alerts to Slack, Discord, or social platforms like Instagram. CRM records can be created or updated from entries. Location data can be forwarded to delivery APIs such as ShipEngine or Uber Eats, and numeric values can be sent to analytics tools like Google Analytics.

None of these are hard-coded integrations. They work because the plugin lets you describe the request. If a service offers a REST endpoint, you can reach it.

Getting Results

A typical setup begins with a connection profile. You enter the base URL and authentication for the service, add any headers it requires, and attach a schema if one is available. Then you open a form, add a feed, choose the profile, select the endpoint and method, and map form fields to the parameters or body. Schema-assisted mapping helps here, since it flags invalid parameters before you test rather than after.

Testing is straightforward because every submission leaves a trace. If a request fails because of a typo in a field mapping or a temporary outage on the remote side, open the entry and retry the feed. When a campaign produces a batch of failures, Feed Forge lets you retry them in bulk instead of one at a time.

For forms that need live data on the way in, connect the same profile to Populate Anything. A product selector can list items from an inventory service, or a field can show a value returned by a lookup. Visitors see current information without anyone editing the form.

The result is a form that does more than record an entry. It sends data on, receives answers, and keeps the whole exchange visible inside the WordPress admin. Teams stop re-keying data, and developers stop maintaining one-off webhook code for every new service.

Frequently Asked Questions

Does GC API Alchemist slow down form submissions?

Not by default. Feeds are processed asynchronously, so the visitor reaches the confirmation without waiting for the external service. The exception is the option that requires a response to complete submission, which you enable deliberately for forms that depend on an immediate answer.

What happens if the API replies long after the form was submitted?

The plugin can generate a callback URL ahead of time. When the remote service finishes its work, it sends the result to that URL, and the plugin updates the matching entry. This keeps slow or batch-style processes tied to the right submission.

Can I reuse one set of credentials across several forms?

Yes. API Connection Profiles hold the base URL, authentication, headers, and schema in one place. Any number of feeds can reference a profile, so a credential change happens once. Profiles can also drive Populate Anything field population.

Is the plugin GPL licensed, and does my data pass through a third party?

The plugin is released under the GPL license. It is built on the Gravity Connect framework, and your form data travels from your WordPress site directly to the endpoints you configure. It does not touch the vendor’s servers on the way.

Category: