Neon CRM
CRMRun nonprofit operations against Neon CRM: agents create and search constituent accounts, record donations against the right campaign and fund, enroll memberships, log activities, and pull pledges, grants, and event registrations for reporting.
What This Integration Enables
In a nonprofit, the CRM is not just a contact list. It is the audit trail behind every receipt, grant report, and board number. A donation recorded against the wrong fund is not a data-entry slip, it is an accounting problem that surfaces months later in front of an auditor. This connector treats Neon CRM with that seriousness: agents resolve campaigns and funds from List Campaigns and List Funds before a gift posts, match donors by search instead of assumption, and leave an activity trail on the constituent record for every automated touch. FlowRunner agents handle the operational load: creating and searching constituent accounts, recording donations, enrolling memberships, logging activities, and pulling pledges, grants, and event registrations for reporting. The development team keeps the work that is actually theirs, donor relationships and judgment on ambiguous records, through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop/) steps.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Online gifts post themselves, correctly
A gift settles in [Stripe](/integrations/stripe). The agent runs Search Accounts against the donor's email. On a clean match, Create Donation records the gift with the campaign and fund resolved from the designation the donor chose. When there is no match, Create Individual Account adds the constituent first. When there are two plausible matches, a married couple sharing an email, a donor with two records, the agent stops and asks a gift officer in [Slack](/integrations/slack) before anything posts. Gift entry stops being a backlog, and the giving history it feeds stays trustworthy.
Event registrants become stewarded constituents
Before an event, the agent pulls the attendee list with Get Event Registrations and posts a staffing summary to the events channel. When a ticket buyer comes in through [Eventbrite](/integrations/eventbrite), Create Individual Account adds them as a constituent and Create Activity logs the registration as an interaction, so the relationship starts on the record rather than in a spreadsheet nobody reconciles. After the event, follow-up activities queue for the development team while attendance is still fresh.
Month-end reconciliation without the export ritual
On a monthly cadence, the agent walks List Donations for the period and writes each gift to [Google Sheets](/integrations/google-sheets) for the finance review, or posts payments into [QuickBooks Online](/integrations/quickbooks-online) for reconciliation. Pledge balances from List Pledges and grant status from List Grants land in the same report. The bookkeeper reconciles against a dataset that came straight from the system of record, and month-end stops depending on someone remembering the export steps.
Human-in-Loop Highlight
Neon CRM's Delete Account permanently deletes a constituent and its associations, and the API is blunt that it cannot be undone. For a nonprofit, what that removes is giving history, the substance of year-end tax receipts, donor anniversaries, and grant reports. So when a dedup agent finds two records for the same donor, it does not consolidate on its own. It pulls both with Get Account, sums what each record carries, and asks the gift officer: "Two accounts match Eleanor Vance. Account 3301 holds eight years of giving and an active pledge. Account 4187 has one gift from last spring's event. Move the event gift's context to 3301 and delete 4187?" The agent acts only on the answer. A donor's history is the one asset a development office cannot recreate, so no agent deletes it unattended.
Agent Capabilities
28 actionsConstituent Accounts
7- List Accounts Lists individual and company constituents with type filters and pagination. Used for sweeps and enrichment runs.
- Search Accounts Runs field-based advanced search across constituents. The donor-matching step before any gift posts.
- Get Account Retrieves a constituent's full record with contact details and custom fields. Used to load history before merge or stewardship decisions.
- Create Individual Account Creates a person constituent from a first and last name. Used when a new donor or registrant appears.
- Create Company Account Creates an organization constituent with an optional primary contact. Used for corporate donors and sponsors.
- Update Account Updates a constituent with a full account payload. Used for structured corrections.
- Delete Account Permanently deletes a constituent and its associations. Cannot be undone; always behind a human decision.
Donations
3- List Donations Lists donations with amounts, dates, and campaign and fund attribution, optionally per account. The backbone of reconciliation.
- Get Donation Retrieves a single donation with donor, campaign, fund, and payment detail. Used for gift-level review.
- Create Donation Records a gift against a constituent with campaign and fund attribution. The core gift-entry action.
Memberships
3- List Memberships Lists memberships with levels, terms, and status, optionally per account. Used for renewal sweeps.
- Get Membership Retrieves a membership with level, term dates, and fee. Used before renewal outreach.
- Create Membership Enrolls a constituent at a membership level with term and fee. Used when a signup or payment confirms membership.
Events
3- List Events Lists events with dates, locations, and capacity. Used to find upcoming events for follow-up flows.
- Get Event Retrieves an event with schedule, capacity, and financials. Used to load event context.
- Get Event Registrations Lists registrations for an event with attendees and status. The input for reminder and stewardship workflows.
Activities
3- List Activities Lists interactions, tasks, and notes, optionally per account. Used to review the touch history.
- Get Activity Retrieves an activity with subject, note text, and status. Used for detail on a specific touch.
- Create Activity Logs an interaction, task, or note against a constituent. Used so every automated touch leaves a trail.
Orders and Pledges
4- Get Order Retrieves an order with line items, totals, and payment status. Used for purchase-level detail.
- Create Order Creates an order from a full payload covering line items, donations, and payment. Used for structured transactions.
- List Pledges Lists pledges with schedules and remaining balances. Used for pledge-fulfillment reporting.
- Get Pledge Retrieves a pledge with installments and balance. Used before reminder outreach.
Campaigns, Funds, and Grants
5- List Campaigns Lists fundraising campaigns with goals and status. Used to resolve valid campaign IDs before gifts post.
- List Funds Lists funds with codes and status. Used to hold fund discipline on every donation.
- List Custom Fields Lists custom fields per component such as Account or Donation. Used to discover valid field names before writes.
- List Grants Lists grants with amounts, grantors, and funding periods. Used for grant pipeline reporting.
- Get Grant Retrieves a grant with attribution and purpose. Used for report-ready grant detail.
Frequently Asked Questions
What can FlowRunner do with Neon CRM?
FlowRunner agents can run List Accounts, Search Accounts, and Get Account in Neon CRM, plus 25 more actions.
Does connecting Neon CRM to FlowRunner require OAuth?
No. Neon CRM connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Neon CRM trigger a FlowRunner workflow automatically?
Neon CRM doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Neon CRM
$100 in credits. No card required. Connect in minutes.