How to Connect Store Leads to n8n

Store Leads holds records for several million active Shopify, BigCommerce, and WooCommerce stores, including the apps each one loads, an estimated monthly order band, the shipping page text, and a change history. In the 3PL warehouse system it carries source 1, the highest-intent feed, because an app install or an order band move is the moment a brand’s own fulfillment stops working. The workflows query it daily for changed stores and weekly to re-check every domain already on the list.

What you need

• A Store Leads plan that includes API access. The 3PL warehouse system prices this at the Standard tier, about $79 per month as of 2026, and holds it separate from the base total so the base figure stays comparable with the other systems in this library.
• The 3PL warehouse workflows imported into a running n8n instance.
• About 10 minutes.

Get the API key

1. Sign in to Store Leads.
2. Open your account settings and find the API section. The key is self-served on paid plans and appears in full only once, so copy it before leaving the page.
3. Store it in your password manager.

If the API section is missing, the plan does not include API access yet. That is a plan change rather than a support ticket, and the free trial tier does not carry it.

Create the credential in n8n

1. Open Credentials and add a Header Auth credential.
2. Name: Authorization. Value: Bearer followed by a space and your key.
3. Save it as “Store Leads LGL”, which is the name the sourcing and watch workflows expect.

Header Auth is a generic credential, so n8n never validates it against Store Leads at save time. It only fails or succeeds when a request runs, which is why the test below matters more than a green save message.

Test it

1. In a scratch workflow, add an HTTP Request node.
2. Method GET, URL https://storeleads.app/json/api/v1/all/domain.
3. Query parameters: filter set to country_code=US,platform=shopify, fields set to domain,platform,apps,estimated_monthly_sales,updated_at, and page_size set to 10.
4. Authentication: Generic Credential Type, Header Auth, “Store Leads LGL”.
5. Execute the step.

You should see ten store records with an apps array on each one. A 401 means the key is wrong or the Bearer prefix is missing. A 403 usually means the plan does not include the endpoint you asked for.

Cost and two gotchas

$79 per month on the Standard tier, and the system page keeps that line separate from its base total. The first gotcha is paging: the response carries a cursor and the query has to send it back, otherwise every daily run returns the same first page and the workflow reports the same stores forever. The second is the per-domain endpoint. Calling it once per row burns a month of plan calls in a single watch run, so WF6 batches 200 domains into one bulk request instead. Both mistakes look like success in the execution log, so check the record count against what you expect on the first few runs.

Where the library uses Store Leads

Only the 3PL warehouse system. Its sourcing workflow reads changed stores daily and keeps the ones whose app list gained or lost a watched app or whose order band moved up, and its store watch workflow re-reads every tracked domain weekly, routing an order band move, a new app, or a disappearing fulfillment partner to three different outcomes.