Connect Zapier, Make and n8n

scoco does not offer its own apps for Zapier, Make or n8n. You connect these tools with a webhook: scoco posts every event you choose as signed JSON to an address your tool creates for you. By the end you will know how to add the endpoint, choose the right events and make the connection in each of the three tools.

Add the endpoint in scoco

First create a receiving address in your tool, as described below. Then:

1. Open Settings›Integrations and go to the Automation card.
2. Click Webhook endpoint. The Add a webhook endpoint window opens.
3. Paste the address from your tool under Address. It must start with https://.
4. Tick what you need under Events. With nothing ticked, scoco sends every event.
5. Click Add.
6. The Signing key window shows the key exactly once. Keep it with Copy key and close with I have saved the key.
7. Click Test next to the new endpoint. scoco sends a signed test event straight away and shows whether it was accepted.

Which events you need

• Summary ready: a call's summary with name, company, reason for calling, urgency and callback number. The usual trigger for a spreadsheet row, a ticket or a message to your team.
• Call ended: arrives earlier, but without a summary, with the number, duration and result.
• Appointment booked, Appointment cancelled, Appointment moved: appointments your assistant booked, and changes to them.
• Contact created, Status changed, Assigned, SMS received, SMS sent.

When each event is sent is listed in the webhook documentation. Your tool shows its fields as soon as the first real event arrives.

Zapier

1. Create a Zap and pick "Webhooks by Zapier" with "Catch Hook" as the trigger.
2. Copy the webhook address Zapier shows and use it to add the endpoint in scoco.
3. Trigger an event and let Zapier pick it up in its test step. Then add your actions.

According to Zapier, "Webhooks by Zapier" is available on paid plans only, not on the free plan.

Make

1. Create a scenario and pick "Webhooks" with "Custom webhook" as the first module.
2. Add a new webhook, copy its address and use it to add the endpoint in scoco.
3. Make waits for the first message and works out the fields from it. Trigger an event for that.

n8n

1. Start the workflow with a "Webhook" node and set its HTTP method to POST. scoco sends every event as a POST.
2. Enter the node's production URL in scoco and publish the workflow (in older n8n versions: activate it). Only then does the production URL receive. The test URL only receives while you are waiting for a test event in the editor.

Real data for field mapping

Test only sends a test event of type ping with a short text message and no call data. For your tool to learn the real fields, trigger a real event: call your scoco number from a phone. Test calls made from the dashboard do not trigger events.

Verify the signature

Every message carries the X-Scoco-Signature header with a timestamp and an HMAC-SHA256 signature made with your key. If your tool allows a code or crypto step, check it there. Compute it over the unchanged body, not over JSON your tool has already parsed, and reject messages older than about 5 minutes. Formula and sample code: webhook documentation.

Common problems

Add cannot be clicked. The address does not start with https://.

The test fails. The message names the reason, for example an HTTP response or a timeout. Your tool must answer within 10 seconds. In n8n, check that the production URL is entered and the workflow is published.

The key is lost. scoco cannot show it again. Choose Remove in the endpoint's menu and add it again.

Nothing arrives any more. If a delivery fails, scoco makes up to 5 attempts in total. If 20 deliveries in a row fail over at least 24 hours, the endpoint is Disabled and the owner receives an e-mail. Fix the cause and choose Enable in the menu. Events from the time in between are not delivered later. The Log shows what was delivered in the last 30 days.