Send leads from Zapier

Connect Zapier to solarOS so any Zap (a web form, a spreadsheet row, another app's webhook) can create a Lead.

Before you start

You need the Owner or Admin role to create the API key Zapier connects with.

Steps

1. Create an API key for Zapier: go to Settings → Connected apps → API keys, click Create API Key, and name it something that says what it's for, for example "Zapier lead intake." Choose Limited access and check exactly these scopes: leads:write, campaigns:read, lead_sources:read, sales_types:read, team_members:read. Setting a Key owner is recommended: it becomes the default Lead owner when a Zap doesn't specify one. Copy the key now; it's shown only once.
2. In Zapier, add a new solarOS connection and paste in that key.
3. Add solarOS's Create Lead action to your Zap and map fields from your trigger: First Name and Last Name (required), Email, Phone, Street Address, City, State, Zip Code, Campaign, Lead Source, Sales Types, Lead Owner (leave blank to use the key's default), Notes, and Submission ID (your trigger's own unique ID, for example a form entry ID; this prevents a duplicate Lead if the same submission retries).
4. Test the step, then publish the Zap.

Check it worked

Triggering the Zap creates a Lead in Sales → Leads with the Campaign, Lead Source, and Sales Type you mapped. Running the same trigger again with the same Submission ID doesn't create a duplicate.

Common problems

• Connection fails, naming missing scopes. Add the missing scopes to the key (see step 1) and reconnect using the same key; you don't need a new one.
• Campaign, Lead Source, or Sales Types dropdowns are empty. The key is missing campaigns:read, lead_sources:read, or sales_types:read. A key without these scopes still connects, but its dropdowns come back empty. Add the scope and reconnect.
• Leads show up without the source you expected. Campaign and Lead Source are separate fields in the Zap step and are easy to swap; check the mapping.

For developers

solarOS's Zapier app is private. Ask solarOS support for the current invite link if you don't already have one. The app authenticates with an API key (see Create and manage API keys) and calls the same public API reference any other integration uses.