Make your first merge

Setup & support

Choose a template, mark the rows that are ready, and keep the resulting files linked to your sheet.

Install MergeKit from Google Workspace Marketplace

Before you start

Use Google Sheets™ in a desktop web browser with access to the MergeKit add-on. You need a native Google Docs™ template and a Google Drive™ folder where your account can create files. An organization administrator may need to allow the add-on. Native mobile Sheets is not a supported setup surface.

Put unique column names in the first row without leading or trailing spaces. In your template, use simple tags that exactly match those headers: a Name column matches <<Name>>. Tags are case-sensitive. Every tag used in the template or filename needs a nonempty value in each generated row.

Set up a merge

Open the desired sheet tab and choose Extensions → MergeKit → Open MergeKit. Complete Google's genuine authorization flow if requested.
Select Choose template and pick your native Google Doc. Select Choose folder and pick the output folder. Use Refresh selected files if the selected names do not appear yet.
Choose a readiness column and value, such as Ready equals yes, or choose all rows. Readiness matching ignores case and surrounding spaces.
Enter a filename pattern, such as Certificate - <<Name>>, and select Google Doc, PDF, or both. A short job identifier is added to filenames.
Select Save settings, then Run ready rows. Keep the sidebar open while it continues through batches. Avoid editing or sorting the sheet during processing.
Open the generated files using the MergeKit Doc and MergeKit PDF columns. Check the output before using it.

PDF-only output also retains the merged Google Doc as a recovery artifact. The original template is preserved. Successful rows are skipped on subsequent runs, even if you later edit their source values.

Errors, retries and deliberately new jobs

Missing value: fill in the named source value, then choose Retry failed rows. If the error occurred before a recovery snapshot was created, the corrected source can be used.

A job already has a snapshot: its inputs are frozen for recovery. A retry uses those original inputs and known output IDs. Changing the source or settings does not rewrite an already-started job.

Uncertain interrupted operation: wait, retry under the same account and inspect the output folder if the error asks you to. Do not clear an uncertain snapshot simply to force another copy. Manual edits to an in-progress output or damaged recovery information can require review before the job can proceed.

Create a fresh job: first stop the current run, save any output links and inspect the folder for existing or uncertain outputs. Then deliberately clear that row's five MergeKit result cells: Status, Doc, PDF, Error and Snapshot. A later run assigns a new job and may create another set of documents. Do not copy a Snapshot cell to another row.

Another account cannot recover my job: recovery is tied to the user who started it. Retry as that original account. The snapshot is visible spreadsheet data with an integrity check, not an encrypted or editable settings field.

Automate a linked Form response

Link your Google Forms™ form to a response spreadsheet using Google's own controls.
Open its response tab as the account that will own the automation. Select the template and folder, configure your merge, and save settings for that tab.
Select Enable form-submit trigger. The trigger processes new rows on this configured tab under your account, including when the sidebar is closed.
Submit fictional test data and inspect the resulting row and files before using the workflow with real responses.
To stop automation, return to the same tab/account and disable the trigger in the sidebar. Do not add a second manual trigger for the same workflow.

Respondents do not authorize MergeKit and receive no email from it. Other spreadsheet editors do not inherit your selected-file access or personal settings. Your account must retain access to the spreadsheet, template and output folder.

If the trigger catches a busy conflict or processing error, MergeKit retains an Automatic processing needs attention notice in the automation owner's personal settings for that tab. Reopen or refresh the sidebar under that account to see the last recorded affected event's row number and time. Row positions can change after a sort. Later successful events do not clear the notice.

Choose Run ready rows for responses that have not started, then Retry failed rows for Error or Working rows. Inspect the result columns and output links; successful rows are skipped. Acknowledge notice only hides that notice. It does not process rows or verify recovery. When another merge holds the spreadsheet lock, the trigger does not change row cells. There is no automatic delayed retry or failure email.

Platform termination or revoked permission can prevent the trigger from recording a notice. Check response statuses periodically and after restoring access, even when the sidebar shows no notice.

Permissions and limits

The add-on requests access to the current spreadsheet, selected or app-created Drive files, its Sheets sidebar/dialogs, Google API requests and optional trigger management. It does not request Gmail, mail-send, full-Drive or broad Docs access. MergeKit also requests Google sign-in identity and email access for billing and allowance checks. Pasting a file ID does not grant selected-file permission; use the file picker.

Use at most 5,000 source rows and 195 source columns. Google API quotas and Apps Script execution limits apply. Large templates or rows can exceed the recovery-cell limit, and Google's PDF export size limit applies. Supported template content is ordinary text exposed by the Docs API, including text runs in tables, headers, footers and document tabs. Images, drawings, loops, expressions and imported jobs from other add-ons are outside the supported tag workflow.

If you switch the active tab while the sidebar is open, close and reopen MergeKit before continuing. Keep each row's recovery and result cells with its source row. Deleting an output file does not trigger automatic recreation.

Plans, allowances and billing

Prices are in USD: Free includes 25 newly admitted merges per Google Account per UTC calendar month; Teacher is $29 per year; Pro is $79 per year; Domain is $299 per year. All paid plans have unlimited MergeKit merges, subject to Google's quotas and the same technical limits. See the plan comparison.

What counts: one row's authorization for new generation uses one merge before any file is created, even if that job later fails. Doc and PDF together count once. Retrying the identical already-authorized saved job reuses its grant after a month change, cancellation or a Stripe outage, provided identity and the stored grant can still be verified. Clearing its recovery state and starting a new job uses another allowance.

Jobs from before billing: an unfinished version-2 or other pre-billing job with no server grant uses one allowance on its first billing-authorized attempt. Later identical retries do not count again. Successful completed rows remain skipped. Keep existing snapshots and outputs; do not reset them to try to avoid counting.

Monthly usage: Free resets at 00:00 UTC on the first day of each calendar month, with no rollover. Manual runs across all spreadsheets and Form automation share your account allowance; Form responses use the automation owner's account, not the respondent's. Paid jobs also contribute to the monthly used count, with no paid-plan cap. If paid access ends, Free has 25 minus that month's total starts remaining, with a minimum of zero.

Teacher and Pro: each plan covers the signed-in Google Account. Teacher has the same merge allowance as Pro and requires you to confirm that you are an educator. Domain: sign in with an account in the covered Google Workspace™ domain. Google must return the matching verified domain; typing that domain or having a similar email address does not qualify. Membership does not require or grant administrator status.

Upgrade and manage: choose a paid plan under Your plan in the MergeKit sidebar, then open Continue to secure Stripe checkout. For Teacher, first confirm that you are an educator. Use Manage billing and then Open Stripe billing management to manage your subscription. Do not send card details to support. Paid plans renew yearly until cancelled. Portal cancellation stops the next renewal and leaves otherwise eligible paid access active through the paid period. A processed refund or payment-risk issue can suspend access sooner. Uninstalling the add-on or disabling a trigger does not cancel billing. Applicable tax, if any, is handled by Innova Apps through its existing process outside Stripe. Stripe Checkout does not automatically calculate tax. Contact support for tax or invoice questions before purchasing.

Changing paid plans: in-place paid-plan changes are disabled. Cancel the current subscription and wait for it to end before buying another paid plan. Only the purchaser can open the subscription's billing portal; ordinary domain members can use the domain plan without managing its billing. A purchaser who leaves the licensed Workspace domain can still manage billing but no longer receives that domain's coverage.

Payment completed, plan not updated: return to the add-on and choose Refresh plan. Plan activation depends on confirmed payment, so a return page alone is not proof of activation. Contact support if the status does not settle. Avoid repeated purchases while a payment is uncertain.

Billing status unavailable: an outage or identity-verification failure is distinct from an exhausted Free plan. New jobs wait until access can be verified. Already-authorized saved jobs can retry during a Stripe outage if the billing service can verify identity and the stored grant; if the billing service itself is unreachable, keep recovery cells and output links and retry when it returns. For Form processing, inspect row statuses and use the recovery actions above. There is no automatic delayed retry or failure email.

Refund requests: Innova Apps offers a seven-day refund policy for new Pro subscriptions. Contact support within seven days of starting the subscription to request it. Other requests, including Teacher and Domain refunds, are reviewed individually; applicable rights remain unchanged. Cancelling stops future renewal but does not itself issue a refund. A processed refund suspends the affected subscription’s paid access and does not itself cancel renewal, so tell support whether you also want the subscription cancelled. Existing saved-job grants remain usable; another eligible plan or remaining Free allowance can still permit new jobs.

Billing data requests: billing records have no automatic deletion. Contact support for verified manual access or deletion review. Removing stored job grants can prevent old jobs from being recognized as already authorized and require a new allowance on retry. Stop automation and review unfinished jobs before requesting removal. Subscription cancellation, data removal and uninstalling are separate steps; Stripe's payment records are handled separately. See the billing privacy details.

For cancellation, charge, refund or account-access questions, contact billing support. Include your account email and a non-sensitive receipt reference when relevant. Never include card numbers, Google tokens, source documents or recovery snapshots.

Draft testing

To leave MergeKit draft testing, request removal from the draft tester list. Send the request to support@innovaapps.ai and include the Google Account email you use for testing. Opening the email link does not send the request or remove your account automatically.

Removal from the draft tester list, disabling a Form trigger, and uninstalling MergeKit are separate steps. If you enabled Form automation, disable its trigger in the sidebar under the same account and sheet tab before uninstalling the add-on.

Contact support

Email support@innovaapps.ai with “MergeKit” in the subject. Include your browser, the action that failed, the error message and whether you were running manually or from a Form trigger. Share a small fictional example when possible. Do not send passwords, OAuth tokens, recovery snapshots or confidential source documents.

For data access, retention and removal information, read the MergeKit privacy policy. We do not promise a fixed support response time.