How can we help you?

1. Overview & System Requirements

The Gravity Forms DeepL Integration Add-on connects WordPress forms directly to DeepL Pro & Free Neural Machine Translation API, widely recognized by linguistic researchers and global enterprises as the world’s most accurate and nuanced AI translation engine. By automatically translating customer inquiries, multi-language survey submissions, foreign language support tickets, and global partnership applications upon form submission, international operations teams streamline cross-border communication without manual copying, costly translation delays, or reliance on rigid client-side browser widgets.

Whether you operate an international hospitality booking portal, multilingual legal onboarding intake, cross-border eCommerce pre-sale inquiries, or multinational academic applications, this add-on processes submitted form fields directly through DeepL API v2 endpoints. Incoming form submissions are translated instantly into your team’s native operational language and appended to entry notes, email notifications, and downstream CRM integrations with zero latency and complete contextual fidelity.

Core Architectural Capabilities

• Dual DeepL API Support: Connects seamlessly to both DeepL API Free (api-free.deepl.com) and DeepL API Pro (api.deepl.com) authentication keys.
• Formality Control Engine: Apply nuanced linguistic tone (formal, informal, or default) for supported European and Asian languages such as German, French, Spanish, Italian, and Japanese.
• Custom Glossary Integration: Pass predefined enterprise glossaries to enforce consistent brand terminology, product naming conventions, and industry jargon during translation.
• Multi-Target Field Routing: Translate specific source fields (e.g., customer comment, inquiry description) into dedicated target hidden fields, entry notes, or translated email notifications without overwriting original raw inputs.
• Automatic Language Detection: Detect the user’s source language automatically when users submit text in unexpected tongues, with optional source language tag recording.

Minimum Environment Prerequisites

2. Step-by-Step API Setup & Authentication

Connecting Gravity Forms to DeepL requires generating a secure authentication key within your DeepL Developer Console and saving it inside WordPress. The add-on supports automated key validation and endpoint auto-detection.

Step 1: Obtain Your DeepL API Key

1. Log in to your account at DeepL.com.
2. Navigate to Account → Plan & Usage and verify your subscription type is either DeepL API Free or DeepL API Pro. Note that regular DeepL Pro Translator accounts do not include API access.
3. Scroll to the Authentication Key for DeepL API section.
4. Click Copy Key. Free tier keys end with :fx (e.g., abcdef12-3456-7890-abcd-1234567890ab:fx), while Pro tier keys do not include the :fx suffix.

Step 2: Configure Global Add-on Settings

1. In your WordPress WP-Admin dashboard, navigate to Forms → Settings → DeepL.
2. Paste your DeepL Authentication Key into the API Authentication Key field.
3. Select your API Account Type:
   • DeepL API Free: Automatically routes requests to https://api-free.deepl.com/v2/.
   • DeepL API Pro: Routes requests through enterprise high-throughput endpoints at https://api.deepl.com/v2/.
4. Click Save Settings & Test Connection. The system performs an instantaneous handshake ping. A green confirmation badge confirms valid authentication, remaining character quota, and server latency.

3. Feed Configuration & Field Mapping

After global authentication is verified, translation workflows are managed per-form through specialized translation feeds. Navigate to Forms → Select Your Form → Settings → DeepL and click Add New Feed.

Feed Configuration Parameters

Field Mapping Architecture

Under the Field Mapping section, select which form fields should be submitted to DeepL for translation. You can map multiple fields simultaneously, including single-line text inputs, paragraph text areas, and user-selected dropdown options:

• Inquiry Subject Line: Map form field {Subject:2} → Store in {Translated Subject:10}.
• Detailed Message Body: Map form field {Message:4} → Store in {Translated Message:11}.
• Detected Language Tracking: Assign a hidden field (e.g., {Source Language Code:12}) to capture the ISO language code detected by DeepL (e.g., ES, DE, JA).

4. Advanced Workflows & Conditional Logic

Enterprise applications rarely process translations in a vacuum. The add-on integrates tightly with Gravity Forms Conditional Logic, notification engines, and third-party feed dispatch ordering.

Scenario A: Conditional Translation by Country of Origin

If your contact form includes a country selector, you can configure conditional execution so translation feeds fire only when needed. For instance, trigger the English translation feed only if Country is NOT United States, United Kingdom, Canada, Australia. This preserves character quota on domestic leads.

Scenario B: Translated Email Notifications for Global Support

When the translation completes during entry processing, the translated field values become immediately accessible in standard Gravity Forms merge tags. In your form notification settings (Settings → Notifications), you can author custom templates that display both original and translated text side-by-side:

5. Error Diagnostics & Troubleshooting Matrix

When API communication fails, the add-on logs granular diagnostic messages to the official Gravity Forms Logging utility (Forms → Settings → Logging). Refer to the diagnostic matrix below for rapid error resolution:

6. Developer PHP Filter Hooks

Software engineers can customize the translation payload, inject custom glossaries, or manipulate translated outputs programmatically via WordPress filter hooks. Add the following code snippet to your child theme’s functions.php or via a dedicated mu-plugin.

<?php
/**
 * Custom DeepL Request Interceptor for Gravity Forms
 * Injects brand glossaries and sets contextual translation parameters.
 */
add_filter( 'gform_deepl_pre_translate_request', function( $request_body, $feed, $entry, $form ) {
    // Check target form ID
    if ( (int) $form['id'] !== 7 ) {
        return $request_body;
    }

    // Attach custom enterprise glossary ID for German translations
    if ( isset( $request_body['target_lang'] ) && $request_body['target_lang'] === 'DE' ) {
        $request_body['glossary_id'] = 'def33412-8812-4c22-b912-984421aa6612';
        $request_body['formality']   = 'more'; // Enforce formal "Sie" address
    }

    // Preserve non-translatable tokens like order numbers or coupon codes
    $request_body['tag_handling'] = 'xml';
    $request_body['non_splitting_tags'] = 'token,code,brand';

    return $request_body;
}, 10, 4 );

/**
 * Log translation completion and append custom audit metadata
 */
add_action( 'gform_deepl_post_translate_response', function( $response, $feed, $entry, $form ) {
    if ( ! empty( $response['translations'][0]['detected_source_language'] ) ) {
        $detected = sanitize_text_field( $response['translations'][0]['detected_source_language'] );
        gform_update_meta( $entry['id'], '_deepl_detected_language', $detected );
    }
}, 10, 4 );

7. Frequently Asked Questions (FAQ)

Related Resources & Official Links