What’s supported
Supported actions
This connector supports:- Read Actions, including full historic backfill and incremental read for all supported objects.
- Proxy Actions, using the base URL
https://api.lightfield.app.
Notes
- Lightfield requires a
Lightfield-Version: 2026-03-01header on every API request. Read Actions send it for you; Proxy calls must include it themselves.
Supported objects
The Lightfield connector supports reading from the following objects:Example integration
To define an integration for Lightfield, create a manifest file that looks like this:Before you get started
To connect Lightfield with Ampersand, you will need a Lightfield account.Creating an API key for Lightfield
- Sign in to Lightfield as an admin (only admins can manage API keys).
- Open the API keys settings page and create a key.
- Grant the read scopes for the objects you need:
accounts:read,contacts:read,opportunities:readandmembers:read. - Copy the key. Lightfield shows it only once.
Using the connector
This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.) To start integrating with Lightfield:- Create a manifest file like the example above.
- Deploy it using the amp CLI.
- If you are using Read Actions, create a destination.
- Embed the InstallIntegration UI component. The UI component will prompt the customer for their API key.
- Start using the connector!
- If your integration has Read Actions, you’ll start getting webhook messages.
- If your integration has Proxy Actions, you can start making Proxy API calls.

