Help Scout → your first short-link workflow

1 Get ready

You need a Help Scout account, one automation service (Make, Zapier or n8n), and a ShortFreeURL workspace with a domain and remaining API allowance. Automation-service fees are separate.

For a cloud workflow, ShortFreeURL must have a publicly reachable HTTPS address with a valid certificate. A localhost URL only works from the same computer; Make or Zapier cannot reach your localhost.

Example use: Create short links for support resources. Choose a record containing a public https:// URL. Keep private-file access permissions unchanged.

2 Open setup and create your key

In ShortFreeURL, open Integrations & API, search for Help Scout, and choose Set up workflow. Read the popup, then select Create workflow key.

Copy the key once into your automation service's protected credential storage. Copy the displayed Links endpoint too. Do not put a key in a public page, screenshot, or shared workflow export.

3 Sign in to the source app

Create a new scenario (Make), Zap (Zapier), or workflow (n8n). Add Help Scout as the trigger and sign in there. Choose a new-record event appropriate for your use case, select the account/list/project, then load one test record.

Find the field containing the destination URL. If a native source trigger is unavailable, use a source-supported webhook or scheduled fetch; check that app's permissions and automation plan.

4 Choose your HTTP setup

Follow one service below. Replace every placeholder with your own value. Send the raw workflow key in Authorization; do not add a Bearer prefix.

Equivalent JSON example (map your actual URL):

{"originalURL":"https://example.com/article","allowDuplicates":false}

5 Test the complete flow

1. Run one test record. A successful create request returns a 2xx response with shortURL.
2. Map shortURL from the HTTP output into the next action (for example, update the source record's Short link field).
3. Open ShortFreeURL → Branded Links. Confirm the destination and domain match the test record.
4. Open the short URL and confirm it reaches the expected destination.
5. Run a second distinct record and confirm its URL is mapped dynamically, not the first sample's URL.

The response above is an example, not a live test result. Each successful creation uses your normal plan allowance.

6 Turn on automation

Save and enable the scenario, publish the Zap, or activate the n8n workflow. Send one real new record and review execution history. Avoid triggering on the same Short link field your final action updates; add a filter so records with an existing short link are skipped.

To stop, pause the automation and disconnect the specific account in ShortFreeURL. Disconnecting revokes that key. For another account, use Add another account and a separate key.

7 If a step fails

401 / invalid key

Check Authorization, remove extra spaces, and replace a revoked key. Never paste your key into a support screenshot.

403 / plan restriction

Check workspace role, active subscription, and integration entitlement.

Quota or rate-limit error

Read the response, check API allowance, and retry only transient rate limits with a delay. Repeated retries do not bypass quotas.

400 / invalid URL or domain

Map a full public https:// destination. Check your workspace has an available domain.

Connection refused / certificate error

Use the public HTTPS endpoint, not localhost. Check hosting and certificate status.

Short link created but not written back

Map shortURL from the HTTP result and check permissions on the source record's target field.

Ask Support with the provider name, failed step, timestamp and redacted response. Do not include credentials.