Use Make’s existing Apify integration and your own Apify account with LinkedIn Company by Domain.
{
"domains": ["stripe.com", "vercel.com", "gitlab.com"],
"maxDomains": 3,
"mode": "resolve",
"includeUnresolved": true,
"concurrency": 3
}
Check the module’s run options and set a charge cap and timeout before execution. Where the native module lacks a required option, configure an Apify task or use the HTTP API with those options explicitly. The n8n workflow’s $0.10 cap does not apply automatically to Make.
Test successful output, an unresolved domain, an empty dataset and actor failure. Confirm the scenario does not automatically create duplicate runs when an HTTP response is delayed.
For direct distribution, use Share → Public scenario page on the saved scenario. For the Make gallery, create and publish a template, then use Request approval. Gallery publication requires Make’s review.
Exported blueprints require users to configure their own connections. Inspect the export and public preview for credentials and private data before sharing.
This guide is not an exported Make blueprint. A native scenario must be built and tested in an authenticated workspace before publishing a scenario link or requesting gallery approval.
Sources: Apify and Make, scenario sharing, template approval.