API documentationVoyced Connect
Ctrl K
Service statusVoyced website
Docs/Build/n8n

Use Voyced with n8n

Use n8n's HTTP Request node or import one of the starter workflows.

Protect your Voyced access from the first test

Your API credentials can access customer information and the functions allowed for that key. Treat the API secret like a password. Store it only in protected server-side settings or a trusted secret store.

  • Never put an API key, API secret or bearer token in public code, browser JavaScript, screenshots, URLs or support messages.
  • Keep Sandbox and Live credentials separate. Give each integration only the permissions it needs.
  • Rotate the secret and disable the old key at once when exposure is suspected.
Read the security checklist
Use your approved secret method
The downloadable workflows contain no real credentials. Configure credentials through your n8n security setup, restrict workflow exports and review saved execution data before enabling Live. Environment-value examples are intended only for controlled self-hosted setups.

Fastest setup

  1. Add an HTTP Request node.
  2. Select Import cURL.
  3. Copy a cURL request from an endpoint page.
  4. Replace placeholders with n8n expressions or protected credentials.
  5. Test in Sandbox.

Recommended workflow

Manual or Schedule Trigger
→
Request token
→
Voyced API request
→
IF or next action
Keep credentials out of workflow exports and execution data
The starter workflows contain no literal credentials. They use self-hosted n8n environment values named VOYCED_SANDBOX_API_KEY and VOYCED_SANDBOX_API_SECRET. For n8n Cloud or another setup, replace those expressions with your approved n8n credentials or secret-management method before running the workflow. Never paste real values into a workflow you may export or share.

Before importing a starter workflow

  1. Choose how your n8n installation securely stores the Sandbox API key and secret.
  2. For self-hosted n8n, the supplied templates can read VOYCED_SANDBOX_API_KEY and VOYCED_SANDBOX_API_SECRET.
  3. For n8n Cloud, open the token node and replace the environment expressions with your approved protected credential setup.
  4. Import the workflow and inspect every node before running it.
  5. Run it manually in Sandbox before adding a schedule.

Starter workflows

Sandbox connection checkRequest a token and run the customer connection test
Download
Low call credit checkRequest a token, read balance and compare a threshold
Download
Active-number snapshotRequest a token and list active telephone numbers
Download

Move a workflow to Live

  1. Keep the Sandbox workflow disabled as a test copy.
  2. Create separate Live credentials or variables.
  3. Change the URL to https://api.voycedconnect.eu/v1.
  4. Run the Live connection test and capabilities request.
  5. Review execution logs for exposed tokens before activation.

Open n8n HTTP Request help