--- title: "Connect DonorPerfect and Lokalise - APIANT.ai" description: "When \"New donor\" fires in DonorPerfect, your agent runs \"Create a Task\" in Lokalise, or \"Contributor Added\" in Lokalise to \"Add contact\" in DonorPerfect." canonical: "https://apiant.ai/connect/donorperfect-to-lokalise" --- # Connect DonorPerfect and Lokalise When **New donor** fires in [DonorPerfect](https://apiant.ai/connections/donorperfect), your agent runs **Create a Task** in [Lokalise](https://apiant.ai/connections/lokalise), or **Contributor Added** in Lokalise to **Add contact** in DonorPerfect. Describe the whole flow and it is built, tested on every scenario and kept running. DonorPerfect **6** triggers DonorPerfect **36** actions Lokalise **16** triggers Lokalise **26** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want DonorPerfect and Lokalise to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What DonorPerfect and Lokalise can do together ### From DonorPerfect to Lokalise - When **New donor** in DonorPerfect then **Create a Task** in Lokalise - When **New gift** in DonorPerfect then **Create Comment** in Lokalise ### From Lokalise to DonorPerfect - When **Contributor Added** in Lokalise then **Add contact** in DonorPerfect - When **Key Added** in Lokalise then **Add new donor gift by email** in DonorPerfect Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with DonorPerfect and Lokalise ## Triggers and actions 22 triggers · 62 actions - Trigger **New donor** Polling trigger. Fires when a new donor is added in DonorPerfect. Polls the dp table ordered by donor_id descending; dedups on each record's donor_id. - Trigger **New gift** Polling trigger. Fires when a new gift (donation) is created in DonorPerfect. Polls the dpgift table ordered by gift_id descending; dedups on each record's gift_id. - Trigger **New or updated donor** Triggered when a donor is added or updated. - Trigger **New or updated gift** Triggered when a gift (donation) is created or modified. - Trigger **Two-way sync new or updated donors** A trigger for two-way syncing new and updated donors, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping. - Trigger **Two-way sync new or updated gifts** A trigger for two-way syncing new and updated gifts (donations), with enhanced on-the-fly mapping. Polls the DonorPerfect dpgift table. - Action **Add code** Adds a new code and description to the DPCODES table. Allows you to add things like new GL Code, Solicitation, Campaign code and other code values administered in the Code Maintenance screen of DPO. - Action **Add contact** Adds a contact (activity/task) record to a donor in DonorPerfect via the dp_savecontact stored procedure. Supply Donor Id, Activity Code, and contact details. - Action **Add donor** Creates a new donor in DonorPerfect via the dp_savedonor stored procedure. Leave Donor Id empty (0) to create; the new donor_id is returned. Common fields: first/last name, address, city, state, zip, email, phones. - Action **Add gift** Creates a new gift (donation) for a donor in DonorPerfect via the dp_savegift stored procedure. Supply Donor Id, Amount, Gift Date and code fields (GL, Solicit, Sub-solicit, Gift Type, Campaign). - Action **Add new donor gift** Creates a new donation (gift) for the donor with the specified ID. - Action **Add new donor gift by email** Creates a new donation for the donor with the specified email. The gift will only be added if the donor's email is found. - Action **Add new pledge** Adds a new pledge to the specified donor. If successful, the pledge's ID is output. - Action **Add other info** Adds an Other Info record to a donor in DonorPerfect via the dp_saveotherinfo stored procedure. Supply Donor Id, and optionally the date and comments. - Action **Add other info by email** Adds "other info" for the first donor found with the given email address. The other info is not added if the email address is not found. - Action **Delete donor** Deletes the donor with the specified Donor Id from DonorPerfect via the dp_deletedonor stored procedure. - Action **Find donor by first and last name** Returns the first donor whose first and last name exactly match, plus how many donors matched - Action **Find filters by name** Returns one or more filters that match the specified name. Supports wildcard matching. An empty result is returned if no matching filter is found. - Action **Get 20 donor field values** Returns up to 20 field values for the specified donor. An error occurs if the donor is not found. - Action **Get active code by description** Returns the code having the specified description. An error occurs if the code is not found or is inactive. - Action **Get active code description** Gets the specified code's description. An error occurs if the code is not found or is inactive. - Action **Get code description** Returns the description for a code value in the specified DPO code field (e.g. GL, CAMPAIGN, SOLICIT) from the dpcodes table. - Action **Get contact** Returns a single DonorPerfect contact (activity) record by its contact ID, with its standard contact columns. - Action **Get donor** Returns all available fields for the donor with the specified Donor ID from the DPO donor (dp) table. - Action **Get donor by email** Returns the DonorPerfect donor whose email address matches the one supplied, with the donor's standard fields. Use Get donor user-defined field values for custom fields. An error occurs if no donor has that email address. - Action **Get donor by email, first name, and last name** Returns all available donor fields if one or more donor matches the email, first name, and last name. No error occurs if a donor is not found, the emitted 'donor_id' will be empty instead. - Action **Get donor default field info** Returns information about the specified donor field. - Action **Get donor default fields** Returns all default fields for donors. - Action **Get donor gifts** Returns all gifts (donations) for the donor with the specified Donor ID from the DPO dpgift table. - Action **Get donors by filter** Returns the donor IDs that match the saved DPO filter with the specified Filter ID, via the dp_filterids stored procedure. - Action **Get donor user-defined field info** Returns information about the specified donor user-defined field. - Action **Get donor user-defined fields** Returns all user-defined donor fields. - Action **Get donor user-defined field values** Returns all user-defined field values for the specified donor. An error occurs if the donor is not found. - Action **Get field display type** Gets the specified field's display type, which can either be "code" or "description" - Action **Get flags by donor ID** Returns the specified donor's flags. No error occurs if the donor is not found. - Action **Get gift** Returns all fields for the gift (donation) with the specified Gift ID from the DPO dpgift table. - Action **Get gift user-defined field values** Returns all user-defined field values for the specified gift (donation). An error occurs if the gift is not found. - Action **Get other info** Returns one DonorPerfect Other Info record by its id, with its standard columns. - Action **List filters** Returns the ID and name of all saved DPO filters that have non-empty names from the dpfilter table. - Action **Post pledge payment** Posts a payment to the specified pledge for the specified donor. - Action **Set gift custom field** Sets one of your organization's custom fields (such as Class) on an existing gift - Action **Update donor** Updates an existing donor in DonorPerfect via the dp_savedonor stored procedure. Supply the Donor Id of the record to update along with the field values. - Trigger **Contributor Added** Triggers when a new contributor is added to a Lokalise project. - Trigger **Contributor Removed** Triggers when a contributor is removed from the selected Lokalise project. - Trigger **Key Added** Triggers when a new translation key is added to a Lokalise project, whether individually or in bulk (import, API or bulk action). Fires once per added key. - Trigger **Key Comment Added** Triggers when someone adds a comment to a translation key in a Lokalise project. - Trigger **Key Modified** Triggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding). - Trigger **Key Removed** Triggers when one or more translation keys are removed from a Lokalise project, whether deleted individually, in bulk, through the API, or moved to another project. Fires once per removed key. - Trigger **Language Added** Triggers when one or more languages are added to a Lokalise project, firing once for each language added. - Trigger **Language Removed** Triggers when a language is removed from a Lokalise project. - Trigger **Poll Tasks** Triggers when a new task is created in a Lokalise project. - Trigger **Project Exported** Triggers when translation files are downloaded (exported) from a Lokalise project. - Trigger **Project Imported** Triggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file. - Trigger **Project Snapshot** Triggers when a snapshot is taken of the selected Lokalise project. - Trigger **Task Created** Triggers when a new translation or review task is created in a Lokalise project. - Trigger **Task Deleted** Triggers when a task is deleted in a Lokalise project. - Trigger **Translation Reviewed** Triggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk. - Trigger **Translation Updated** Triggers when a translation is changed in the selected Lokalise project, either one at a time or several at once through a bulk action, file upload or the API. - Action **Add Contributor** Adds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions. - Action **Add Languages** Adds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms. - Action **Create a Key** Creates a new translation key in a Lokalise project, optionally with its translations, tags, comments and screenshots, and returns the new key. - Action **Create a Task** Creates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages. - Action **Create Comment** Adds a comment to a translation key in a Lokalise project. - Action **Create Project** Creates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project. - Action **Create Snapshot** Creates a snapshot of a Lokalise project, saving its current state so it can be restored later. - Action **Delete a Key** Deletes a key, with its translations, from a Lokalise project. - Action **Delete a Language** Removes a language from a Lokalise project. - Action **Delete a Task** Deletes a task from a Lokalise project. - Action **Download Files** Exports a Lokalise project's translation files as a.zip bundle and returns the download URL of the bundle. - Action **List All Orders** Returns all translation orders placed under a Lokalise team. - Action **List All Tasks** Returns the tasks in a Lokalise project, optionally filtered by title or status. - Action **List All Translations** Returns the translation items of a Lokalise project (one row per key and language), optionally filtered by language, review status, QA issues or task. - Action **List Project Languages** Returns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms. - Action **List Snapshots** Returns the snapshots saved for a Lokalise project, with each snapshot's title and creation details. - Action **Remove Contributor** Removes a contributor from a Lokalise project. - Action **Retrieve a Comment** Returns a single comment left on a key in a Lokalise project, including its text, author and when it was added. - Action **Retrieve a Contributor** Returns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions. - Action **Retrieve a Key** Returns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations. - Action **Retrieve a Task** Returns a Lokalise task, including its status, progress, due date and the languages and assignees it covers. - Action **Retrieve Project** Returns a Lokalise project's details, including its name, type, base language, settings and translation statistics. - Action **Update a Key** Updates an existing key in a Lokalise project, such as its name, description, platforms, tags or flags, and returns the updated key. - Action **Update a Translation** Updates the text and review flags of a translation in a Lokalise project. - Action **Update Language** Updates a language in a Lokalise project, changing its code, name or plural forms. - Action **Upload File** Uploads a localization file to a Lokalise project and queues it for import. Returns the queued import process so you can follow its status. ## Each app on its own - [ **DonorPerfect** DonorPerfect Online (DPO) is fundraising and donor-management software for nonprofits.](https://apiant.ai/connections/donorperfect) - [ **Lokalise** Lokalise is a translation management tool that lets you structure and automate workflows while encouraging...](https://apiant.ai/connections/lokalise) Reviews ## What our customers say ## More from DonorPerfect - [ **DonorPerfect to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/donorperfect-to-hubspot) - [ **DonorPerfect to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/donorperfect-to-salesforce) - [ **DonorPerfect to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/donorperfect-to-slack) - [ **DonorPerfect to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/donorperfect-to-mailchimp) - [ **DonorPerfect to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/donorperfect-to-shopify) - [ **DonorPerfect to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/donorperfect-to-quickbooks-online) ## More into Lokalise - [ **HubSpot to Lokalise** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-lokalise) - [ **Google Sheets to Lokalise** Google Sheets](https://apiant.ai/connect/google-sheets-to-lokalise) - [ **Gmail to Lokalise** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-lokalise) - [ **Google Calendar to Lokalise** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-lokalise) - [ **Google Drive to Lokalise** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-lokalise) - [ **ActiveCampaign to Lokalise** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-lokalise) Questions ## DonorPerfect and Lokalise, answered ### ### What can start an automation from DonorPerfect? Any of DonorPerfect's 6 triggers in the catalog, including New donor, New gift, New or updated donor and New or updated gift. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Lokalise when something happens in DonorPerfect? Any of Lokalise's 26 actions, including Create a Key, Create a Task, Create Comment and Create Project. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Lokalise to DonorPerfect? Yes. When something happens in Lokalise, your agent can act in DonorPerfect too. This page covers both directions: Lokalise's triggers and DonorPerfect's actions are listed here as well. ### ### Do I have to build a connector for DonorPerfect or Lokalise? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use DonorPerfect and Lokalise without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.