Overview

What is GravityMerge AI Architect?

Architect is a setup assistant that uses AI to convert an existing document into a complete document automation workflow. Upload a contract, policy, letter, or other document, and Architect analyses it to identify variable content and generates both a matching Gravity Forms form and a merge-tagged GravityMerge AI template.

What problem does it solve?

Setting up document automation usually means manually reading through a document, deciding what is variable, creating form fields, and inserting merge tags into the template. For a complex document this can take hours. Architect reduces that work to minutes.

Requirements

  • WordPress 6.0 or later
  • PHP 8.0 or later
  • Gravity Forms installed and active
  • An Anthropic API key (uses the key from GravityMerge AI if installed, otherwise provides its own API key field in settings)

Using Architect

Accessing Architect

After activation, you will find Architect as a menu item labelled AI Architect in the WordPress admin sidebar.

Step 1: Upload your document

Click the upload area or drag and drop a .docx file. The file should be an existing document with real content filled in — a completed contract with actual names and dates rather than a blank template. The richer the content, the more accurately AI can distinguish variable fields from fixed boilerplate.

Step 2: Review the AI analysis

After uploading, Architect sends the document to Claude for analysis. This typically takes 5–15 seconds. The review screen shows:

  • Detected fields — each variable element AI identified, with a suggested field label, field type, and confidence level
  • Repeating/list fields — tables and lists with repeating structures, mapped to Gravity Forms List fields with the correct columns
  • Conditional sections — sections of the document that may only apply in certain situations

Before creating anything, you can:

  • Include or exclude individual fields
  • Change the suggested field type for any field
  • Mark fields as required
  • Edit the form title

Review the suggestions carefully. Architect is strong on obvious variables such as names, dates, and monetary amounts, but may occasionally miss a variable or flag fixed content as variable.

Step 3: Create form and template

Click Create Form & Template to generate both outputs:

  • A Gravity Forms form created via the Gravity Forms API with the detected fields properly typed and labelled
  • A merge-tagged template — a .docx file with merge tags inserted in place of the variable content, preserving the document’s existing formatting, styles, and structure

The success screen provides links to both (opening in new tabs so you don’t lose the page). You can then upload the template to GravityMerge AI and link it to the generated form.

Settings

Accessing settings

At the bottom of the Architect page, click the Settings toggle to expand the settings panel.

API key

If GravityMerge AI is installed and has an API key configured, Architect uses that key automatically and the API key field is hidden. If no key is available — whether GravityMerge AI isn’t installed or doesn’t have a key set — an API key field appears in the settings panel.

AI model

Select which Claude model to use for document analysis. The model selector is always available in the settings panel. Sonnet 4.6 is the default and is recommended for most documents. You can choose a different model before uploading a document.

AI prompt instructions

The settings panel shows the plain-English instructions sent to Claude when analysing a document. You can customise these to change how AI identifies fields, what it considers variable, and how it handles conditionals. The technical response format (JSON structure) is fixed and cannot be edited.

You can add domain-specific guidance here — for example, “For employment contracts, always create a field for Notice Period.”

Tips for best results

Use a representative document

Upload a document that has all variable fields filled in with realistic sample data. A completed contract with real names and dates gives Architect much more context than a blank template or one with placeholder text like “[INSERT NAME]”.

Simple documents work best

Architect handles contracts, letters, policies, and similar prose documents very well. Highly complex documents with deeply nested tables, extensive formatting, or unusual structures may need more manual adjustment after generation.

Review conditional logic

Architect can identify sections that appear optional or conditional, but it may not always infer the correct condition. Review any conditional blocks and set the relevant logic in your form.

Expect to refine

For simple documents, the generated template and form may be ready to use immediately. For more complex documents, you’ll want to review the merge tags and may need to make adjustments — but a major part of the setup work will have been done.

Common questions

Do I need GravityMerge AI to use Architect?

GravityMerge AI is not strictly required to run Architect, but the generated template uses GravityMerge AI merge tag syntax. You will need GravityMerge AI to use the template Architect produces.

Does Architect work with any .docx file?

It works best with text-based documents containing real content. Documents that are mainly images, scans, or heavily formatted tables may not analyse well.

Can I re-run the analysis?

Yes. You can upload the same document again or a different one and run the analysis as many times as you like.

What does it cost per analysis?

Each analysis makes one API call to Claude. For a typical document using Sonnet, expect roughly US$0.01–0.05 per analysis.

Does the generated template preserve my document’s formatting?

Yes. Architect works from your original .docx file. It replaces the variable content with merge tags while preserving the document’s existing formatting, styles, and structure.

Will the template be perfect?

That depends on the nature and complexity of the document. Simple letter templates with obvious variable content will likely be correct. For more complex documents, you’ll want to check the merge tags and may need to make some adjustments, but a major part of the grunt work will have been done.