Skip to content

Integrations and automations

Your grants system, connected to everything else.

Since 2018 I've built more than 40 integrations that move data between grants systems and the tools foundations run on. Your staff stop downloading from one system and uploading to another, and the numbers stop drifting apart.

What can you connect a grants system to?

Almost anything with an API. The systems I've connected most often:

  • Grants management: Fluxx, and Grantseeker connected to Fluxx
  • Finance and ERP: Bill.com, NetSuite, Sage Intacct, SAP and SAP Concur, Business Central, QuickBooks, PeopleSoft
  • Payments and banking: bank payment files and APIs, Stripe, SS&C GoWire, exchange rates from the Bank of Canada and Currency Layer
  • E-signature: Adobe Sign, OneSpan, DocuSign
  • CRM and outreach: Salesforce, Microsoft Dynamics CRM, Neon CRM, Constant Contact, Mailchimp
  • Email and files: Gmail, Outlook, Slack, SharePoint, Google Drive
  • Data: SAM.gov, Google Maps, OpenStreetMap
  • Fluxx
  • Bill.com
  • Oracle NetSuite
  • Sage Intacct
  • SAP Concur
  • Salesforce
  • Adobe Sign
  • Intuit QuickBooks
  • Neon CRM
  • Slack
  • Google Drive
  • OpenAI
  • Anthropic
  • Neo4j
  • SAM.gov
  • SAP
  • Dynamics 365 Business Central
  • OneSpan
  • DocuSign
  • Grantseeker
  • Constant Contact
  • Mailchimp
  • Microsoft Dynamics 365 CRM
  • PeopleSoft
  • SS&C GoWire
  • Stripe
  • Bank of Canada
  • currencylayer
  • Gmail
  • Outlook
  • SharePoint
  • Google Maps
  • OpenStreetMap

Fixed steps for what must be exact

Payments, agreements and finance records need to happen the same way every time. An integration does exactly that: when a status changes, a button is pressed or a schedule runs, the data moves, and the result comes back to your grants system.

Manual work isn't only slow, it's where errors come from. A payment amount typed twice, a bank detail copied by hand, a notification sent with the wrong figure. Automation takes the person out of the copying, not out of the decision.

Example: agreements that send and file themselves

At a national health nonprofit, every grant agreement took six manual steps. Now one status change sends it for signature, and the signed copy files itself back. Their team estimated the streamlined agreement process saves hundreds of thousands of dollars in staff time.

Before: 6 manual steps per agreement

  1. Download the agreement from the grants system
  2. Upload it to the e-signature system
  3. Copy and paste each signer's email
  4. Send it, then wait
  5. Download the signed copy
  6. Upload it back to the grants system

After: 1 step

Change the status in the grants system. Done.

Which platform do you build on?

The one you already own. I build with Workato, Power Automate or Zapier, or write custom code when none of them fits, and choose the least complex option that reliably does the job.

Six questions we work through together

The first call starts with these. In integration discovery, the answers become the design:

  1. What business process or problem will this solve?
  2. What data has to move: organizations, payments, documents?
  3. What triggers the move: a status change, a button, a schedule?
  4. One-way push or bi-directional?
  5. Does the other system have an API, and a connector on the platform you own?
  6. What comes back, and what should your grants system do when it does?

How does a project work?

  1. 1 · FreeTalk it throughA free 30-minute call. We walk your process through six questions and size what discovery would take.
  2. 2 · Bucket of hoursIntegration discoveryA bucket of hours, sized on that call. Together with your team, I map the systems, triggers, filters, steps, special logic and field mappings, one-way or two-way, into an integration design document. The integration design document is yours. When it's done, you choose who builds the integration: me, your own team, or another partner. Most clients have me build it.
  3. 3 · Fixed scopeBuild and go liveThe design becomes the scope of work, so you get a fixed price with no surprises. I build it in your test environment, your team tests it, we refine it, and we go live together with a smoke test in production. The design document stays current throughout, and you can see the integration logs.

Support when you need it. Unused discovery hours roll over to support or further advice, or you can add a bucket of hours later. Projects can be contracted directly with me or through Fluxx if you'd rather have one contract.

On Fluxx? See what I've built for Fluxx customers.

Where is your team losing time?

Let's talk it through. A free 30-minute call to walk your process through six questions and size what discovery would take.

Book a 30-minute call