Source connector

Little Green Light connector

Little Green Light integration for databases, warehouses and BI tools

Fundraising CRM for small nonprofit development teams. Datrise captures Little Green Light entities such as constituents, gifts, pledges, campaigns, events and volunteer records, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Little Green Light REST API v1 authenticates with API key, incremental runs key on updated_at, and Little Green Light caps calls at 300 API calls per any rolling 5-minute period; the docs state calls beyond that threshold are simply ignored rather than queued or rejected with a specific error code.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `little_green_light_constituents`) with a schema derived from the Little Green Light API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Little Green Light pipeline page, and join the waitlist to get the Little Green Light connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Little Green Light data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
constituents	little_green_light_constituents	Upsert by primary key, incremental on updated-at
gifts	little_green_light_gifts	Upsert by primary key, incremental on updated-at
pledges	little_green_light_pledges	Upsert by primary key, incremental on updated-at
campaigns	little_green_light_campaigns	Upsert by primary key, incremental on updated-at
events	little_green_light_events	Append-only, incremental by timestamp
volunteer records	little_green_light_volunteer_records	Upsert by primary key, incremental on updated-at

Little Green Light API: setup facts for the connector

Verified against the vendor documentation on 2026-09-21. Unknown values are left blank rather than guessed.

API	Little Green Light REST API v1
Authentication	API key — A per-account API key is generated under Settings > Integration settings, then presented as the username in HTTP Basic Auth (blank password), as an `access_token` query parameter, or as a `Bearer` Authorization header; all three are the same static key, not separate credential types.
Pagination	offset — List and search endpoints (e.g. `GET /api/v1/constituents`) take `limit` (default 25) and `offset` (default 0); responses do not appear to expose a total count in the documented examples, so paging continues until a short page is returned.
Rate limit	300 API calls per any rolling 5-minute period; the docs state calls beyond that threshold are simply ignored rather than queued or rejected with a specific error code
Incremental cursor	updated_at — Constituent search supports `q[]=updated_from=...;updated_to=...` (RFC3339) to filter by the same value returned as `updated_at` on each record, but the `sort` parameter names it differently (`date_updated`), which is easy to typo when building an incremental query.
Webhooks	No
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Little Green Light

The published rate limit is 300 calls per any 5-minute window, and the API terms say excess calls are silently ignored rather than returning a documented 429 status, so a naive client can lose requests without an obvious retry signal.
"Webhooks" in LGL's integration settings are inbound only — they let an external tool push data into LGL's Integration Queue — there is no outbound webhook or change-notification feed a connector can subscribe to.
There is no bulk export endpoint or documented soft-delete/`deleted` flag anywhere in the API reference; DELETE endpoints exist for appeals, campaigns, categories, and class affiliations but detecting a deletion requires diffing full ID lists, not polling a timestamp.
Not all account fields are exposed via the API by default; LGL says missing fields must be requested individually from support@littlegreenlight.com before they appear in responses.

Compare this against every other documented API

Popular destinations for Little Green Light

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Little Green Light connector FAQ

What Little Green Light data does the connector extract?: 6 objects: constituents, gifts, pledges, campaigns, events and volunteer records. Each lands in its own table with types preserved; history-style objects (1: events) load as append-only streams.
Is the Little Green Light integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Little Green Light data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Little Green Light → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Little Green Light pipeline with guided onboarding

Join the waitlist to get priority access for Little Green Light integrations with guided setup, schema-aware mapping, and production-grade incremental sync.