Integration
Connect DonorPerfect to Neon Postgres
When something happens in DonorPerfect, your agent does the next thing in Neon Postgres. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want DonorPerfect and Neon Postgres to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What DonorPerfect can start in Neon Postgres
When New donor in DonorPerfect
then Add branch in Neon Postgres
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 Neon Postgres
Triggers and actions 6 triggers · 61 actions
- 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.
- 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.
- New or updated donor
Triggered when a donor is added or updated.
- New or updated gift
Triggered when a gift (donation) is created or modified.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- Add new donor gift
Creates a new donation (gift) for the donor with the specified ID.
- 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.
- Add new pledge
Adds a new pledge to the specified donor. If successful, the pledge's ID is output.
- Add other info
Adds an Other Info (user-defined) record to a donor in DonorPerfect via the dp_saveotherinfo stored procedure. Supply Donor Id, the field name and value.
- 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.
- Delete donor
Deletes the donor with the specified Donor Id from DonorPerfect via the dp_deletedonor stored procedure.
- 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.
- Get 20 donor field values
Returns up to 20 field values for the specified donor. An error occurs if the donor is not found.
- Get active code by description
Returns the code having the specified description. An error occurs if the code is not found or is inactive.
- Get active code description
Gets the specified code's description. An error occurs if the code is not found or is inactive.
- 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.
- Get donor
Returns all available fields for the donor with the specified Donor ID from the DPO donor (dp) table.
- Get donor by email
Returns the DonorPerfect donor whose email address matches the one supplied, including the donor's user-defined field values. An error occurs if no donor has that email address.
- 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.
- Get donor default field info
Returns information about the specified donor field.
- Get donor default fields
Returns all default fields for donors.
- Get donor gifts
Returns all gifts (donations) for the donor with the specified Donor ID from the DPO dpgift table.
- 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.
- Get donor user-defined field info
Returns information about the specified donor user-defined field.
- Get donor user-defined fields
Returns all user-defined donor fields.
- 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.
- Get field display type
Gets the specified field's display type, which can either be "code" or "description"
- Get flags by donor ID
Returns the specified donor's flags. No error occurs if the donor is not found.
- Get gift
Returns all fields for the gift (donation) with the specified Gift ID from the DPO dpgift table.
- 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.
- List filters
Returns the ID and name of all saved DPO filters that have non-empty names from the dpfilter table.
- Post pledge payment
Posts a payment to the specified pledge for the specified donor.
- 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.
- Add branch
Create a new branch in a Neon project.
- Add compute endpoint
Creates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write endpoint and multiple read-only endpoints.
- Add database
Creates a new Postgres database in a Neon project branch, owned by an existing role.
- Add project
Creates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details.
- Add role
Creates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies.
- Delete branch
Delete a branch by project_id and branch_id.
- Delete compute endpoint
Deletes a compute endpoint from a Neon project. Existing connections to the compute are dropped. If the compute does not exist or was already deleted, the step still succeeds with an empty result.
- Delete database
Deletes the specified database from a branch of a Neon project.
- Delete project
Deletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days.
- Delete role
Deletes the specified Postgres role from a Neon branch.
- Get branch
Retrieves details of a branch in a Neon project.
- Get compute endpoint
Retrieve details about a compute endpoint.
- Get connection URI
Retrieve a Postgres connection URI for a database/role/branch/endpoint combination.
- Get database
Retrieves details of a database on a Neon project branch.
- Get project
Retrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics.
- Get role
Retrieves details about a Postgres role (user) on a Neon branch.
- Get role password
Retrieves the password for a Postgres role on a Neon branch.
- List branches
Retrieve a list of branches for a Neon project.
- List compute endpoints
Lists the compute endpoints (Neon compute instances) in a project.
- List databases
Lists the databases on a branch of a Neon project.
- List operations
Lists the operations (asynchronous actions such as starting a compute or creating a branch) Neon performed on a project. Operations older than 6 months may no longer be available.
- List projects
Lists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization.
- List roles
Lists the Postgres roles on a Neon project branch.
- Start compute endpoint
Start (resume) a suspended compute endpoint.
- Suspend compute endpoint
Suspends the specified Neon compute endpoint (scales it to zero).
- Update branch
Update a branch's properties (e.g. name, protected) by project_id and branch_id.
- Update compute endpoint
Updates an existing compute endpoint in a Neon project by ID.
- Update database
Updates the name or owner of a database on a Neon project branch.
- Update project
Update settings for a Neon project by project_id.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from DonorPerfect
DonorPerfect to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DonorPerfect to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DonorPerfect to MailchimpMailchimp marketing automation and email platform.
DonorPerfect to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
DonorPerfect to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
DonorPerfect to SendGridSendGrid by Twilio — email delivery and marketing platform.
More into Neon Postgres
Salesforce to Neon PostgresSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to Neon PostgresGoogle Sheets
Gmail to Neon PostgresGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Neon PostgresGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
DonorPerfect and Neon Postgres, 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 Neon Postgres when something happens in DonorPerfect?
Any of Neon Postgres's 29 actions, including Update branch, Update compute endpoint, Update database and Update project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Neon Postgres to DonorPerfect?
Neon Postgres has no triggers in the catalog today, so automations start in DonorPerfect. If you need the other direction, ask: your agent reads Neon Postgres's API documentation and adds it.
Do I have to build a connector for DonorPerfect or Neon Postgres?
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.
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.