Integrate with DeepL

The Good Grants DeepL integration automatically translates content submitted in an application form into another language. This helps reviewing panels when applications are submitted in multiple languages. It can also support multilingual panels during reviewing.

This integration requires an active DeepL subscription and incurs usage costs. Contact support for more information. 

Common uses

Use case Description
Multilingual reviewing Translate applications into a common language for reviewers.
International programs Support applications submitted in multiple languages.
Reviewer accessibility Help reviewers understand content without manual translation.

Available languages

The integration can currently detect over 100 languages and can translate the detected language into any of these supported languages:

  • Arabic
  • Bulgarian
  • Chinese (simplified)
  • Chinese (traditional)
  • Czech
  • Danish
  • Dutch
  • English (British)
  • English (American)
  • Estonian
  • Finnish
  • French
  • German
  • Greek
  • Hebrew
  • Hungarian
  • Indonesian
  • Italian
  • Japanese
  • Korean
  • Latvian
  • Lithuanian
  • Norwegian Bokmål
  • Polish
  • Portuguese (Brazilian)
  • Portuguese (European)
  • Romanian
  • Russian
  • Slovak
  • Slovenian
  • Spanish
  • Swedish
  • Thai
  • Turkish
  • Ukrainian
  • Vietnamese

Step 1: configure your application form

Start by setting up your form as usual. Add categories, tabs, and fields so you can collect information from applicants. Your translation fields will be separate copies of the original fields. These receive the translated text.

To create fields for translated content:

  1. In the Manage go to Settings > Applications > Fields
  2. Tick the fields you want to translate
  3. Open the Action drop-down and select Copy
  4. Wait for the copied fields to appear in the list with “(copy)” in the title
  5. Select a copied field to edit it
  6. Update the label and short title so you can identify it during field mapping
  7. Move the field to another location in the form if needed
  8. Select Save
  9. Repeat for any additional fields

Step 2: configure the integration

Each integration instance supports one language. 

  1. In the Manage workspace, go to Settings > Integrations > Marketplace
  2. Under 'Translation', select DeepL
  3. In the popup, select Configure
  4. Edit the integration name if needed, then select Next
  5. Review the information in the 'Connect' step and select Next
  6. In 'Events', choose how to trigger the translation
    • On application submitted: triggered when the applicant submits the application
    • On application tagged: triggered when a chosen tag is applied to the application (case-sensitive)
  7. In 'Resources', select your desired forms and languages
  8. In 'Resource mapping', choose your form and the language to translate to—each form can be translated into as many supported languages as you need
  9. Click Add to Application Resource Map to choose additional forms and languages as needed
  10. Go to the 'Field mapping' tab
  11. Select Add to field map for each field you want to translate
  12. Pair each original field with its translation field
  13. Repeat for additional language and form pairings
  14. Select Finish

Fields are translated when an application is submitted or resubmitted—not when it is saved. If you have selected a grant report to be translated on submission you will need to enable this by navigating to Settings > Integrations > Webhooks, clicking into the webhook, and checking the box next to Grant report submitted.

Good to know

  • The DeepL integration is a paid add-on.
  • Contact the client success team to activate or trial the integration.
  • Use copied fields as translation destinations to retain the applicant's original text.
  • You can place translation fields in a separate tab.
  • You can hide translation fields from applicants by deselecting the Read, Write, and Required field access options.
  • This integration is designed to work best with text (single and multi-line) and table fields. Fields with fixed answer options, like drop-down lists, radio buttons, and checkbox fields are not recommended. 

FAQs

Do I need to purchase an account with DeepL?

Yes. An active DeepL subscription is required to use this integration. 

Is there an ongoing cost with GoodGrants? 

Yes. Subscription and usage costs are incurred. Contact support for more information. 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more