Lockally

      Use your API key in the examples

      Replaces lk_live_… in the code samples on this site so you can copy and run them. It is stored in this browser only and is never sent anywhere, including to Ask AI.

      It will be visible on the page. Use a test key if you are sharing your screen or taking screenshots.

      Zapier, n8n, Make and WordPress

      All four integrations are built and their source is public under github.com/lockallyinc. They are not all installable the same way, and this page says which is which rather than implying they are interchangeable.

      What all four need first

      Every integration authenticates with an ordinary Lockally API key. Nothing here uses a different credential type, and none of them needs OAuth.

      1. Create a key in the dashboard, or with POST /v1/api-keys from a key holding tenant:admin.
      2. Give it only the scopes the automation uses. For sending, that is send:write. An automation key living in a third-party platform should never carry tenant:admin.
      3. Use a test key (lk_test_…) while you build. Its sends are simulated, so a misconfigured loop does not mail anybody. See Live and test keys.

      n8n

      The only one you can install without talking to us.

      1. In n8n, go to Settings → Community nodes → Install.
      2. Enter n8n-nodes-lockally and confirm.
      3. Add a Lockally credential and paste the API key.

      Self-hosted n8n only: community nodes are not available on n8n Cloud’s starter tiers. The node’s source is at lockallyinc/n8n-nodes-lockally.

      WordPress

      The plugin hooks pre_wp_mail, so it takes over wp_mail() for the whole site. Every plugin that sends mail through wp_mail(), including WooCommerce and your contact forms, goes through Lockally once it is active. Nothing needs reconfiguring individually, and nothing opts out.

      1. Download the latest zip from lockallyinc/lockally-wordpress releases.
      2. Plugins → Add New → Upload Plugin, choose the zip, activate.
      3. Under the plugin’s settings, enter the API key and the From address.

      The From address must be on a domain you have verified, or every send is refused with 403. Verify it first under Domains and see Domain verification.

      Zapier and Make

      Both are built and both are private. The source is at lockallyinc/lockally-zapier and lockallyinc/lockally-make.

      For Zapier you can deploy the app to your own Zapier account with their CLI (zapier register, zapier push), which is the supported route until the public listing exists. Make’s app is a JSON app definition that can be imported into a Make developer account the same way.

      If neither suits, the API underneath is small enough to wire directly from any platform that can make an HTTP request: see Your first API request. A send is one POST /v1/send with a bearer token and an Idempotency-Key.

      When something does not arrive

      The order to check, because the first two account for most of it:

      1. A 200 is not a delivery. A 202 means queued. A 200 means nothing was queued: every recipient was suppressed, or you used a test key. Both are successes and neither produces a real message. See Understanding responses.
      2. Triggers on Free return nothing, as above.
      3. The From domain is unverified, which is a 403 rather than silence.
      4. Check Message logs for the send, then Suppressions.