AUTOMATION GUIDE

Connect eWork Social to Make, n8n, Zapier and your own tools

Get alerts when leads arrive or deals move, let your automations update your CRM and schedule posts, and send website forms straight into your pipeline. No code needed.

See the templatesEvents and API reference

How it works

There are three ways to connect, and you can use any combination. Each one is switched on from Settings, then Integrations, inside the app, and has a small question-mark button that explains it in place.

WEBHOOKS

Events going out

eWork Social sends a message to your tool the moment something happens: a lead arrives, a deal changes stage, a note or task is added, a post is published or fails. Your tool then does the next step.

Growth plan and above

API KEYS

Actions coming in

Your tool can do things inside eWork Social: add a contact, move a deal to a new stage, add a note or task, or schedule a post. You create a key, choose what it may do, and paste it into your tool.

Agency Pro plan and above

LEAD CAPTURE

Website forms in

Give your website form a private address. Every submission becomes a lead in your CRM with the source set to Website, and fires the new-lead event so your automations run.

Growth plan and above

Which one do I need?

I want toUse
I want to be told when something happensWebhooks
I want my tool to create or change things in eWork SocialAPI keys
I want my website contact form to add leads to the CRMLead capture
I want both: a form becomes a lead, and a team alert goes outLead capture plus a new-lead webhook

Starter templates

Each template shows the eWork Social side once, then the steps for Make, n8n and Zapier. Open the tool you use. n8n templates come as files you can import.

New website lead to Google Sheet and a Slack alert

A visitor fills in your contact form. They land in your CRM as a lead, a new row is added to a Google Sheet, and your team gets a Slack message.

Needs: Growth plan or above. No API key needed.

In eWork Social

  1. Go to Settings, then Integrations, then Website lead capture, and press Add form link. Copy the address it shows and point your website form at it (the How to connect your form section under the link has copy-ready steps for WordPress, Make, n8n and plain HTML).
  2. Under Webhooks, add your tool address (from the steps below), tick New lead (CRM), and press Create. Then press the blue Send test button.
Make
  1. Create a new scenario. Add the Webhooks app and choose Custom webhook. Press Add, give it a name, and copy the address.
  2. Paste that address into eWork Social under Webhooks and press Send test.
  3. Back in Make, the webhook module should say it successfully determined the data structure. If it does not, press Run once and send the test again.
  4. Add Google Sheets, then Add a Row. Map the data fields: name, email, phone, company, source, message.
  5. Add Slack, then Create a Message. Pick the channel from the drop-down list, or type its exact name in lowercase with dashes instead of spaces. Invite the Make app to that channel first, otherwise Slack answers channel_not_found. Write something like: New lead from the website, with the name and email fields inserted. The Send test event only holds a sample message, so name and email stay empty until a real lead arrives.
  6. Switch the scenario on.
n8n
  1. Download the starter file below. In n8n choose Import from File.
  2. Open the first node (eWork event) and copy its Test URL. Paste it into eWork Social under Webhooks and press Send test. You should see the data arrive in n8n.
  3. Replace the two nodes marked ADD HERE with a Google Sheets Append Row node and a Slack Send Message node, using your own credentials. The previous node already provides name, email, phone, company, source and message.
  4. When it works, switch the workflow to Active, copy the Production URL from the first node, and replace the Test URL in eWork Social with it.

Download the n8n file

Zapier
  1. Create a Zap. For the trigger choose Webhooks by Zapier, then Catch Hook. Copy the Custom Webhook URL.
  2. Paste it into eWork Social under Webhooks and press Send test. In Zapier press Test trigger.
  3. Add the action Google Sheets, then Create Spreadsheet Row, and map name, email, phone, company and source from the data section.
  4. Add the action Slack, then Send Channel Message.
  5. Publish the Zap. Webhooks by Zapier is a premium app, so check that your Zapier plan includes it.
What the data looks like
{
  "id": "evt_9f2c1a7b4d3e5f60a1b2c3d4",
  "event": "lead.created",
  "workspaceId": "cm0example",
  "createdAt": "2026-11-18T11:40:02.000Z",
  "firedAt": "2026-11-18T11:40:02.000Z",
  "data": {
    "clientId": "cmw0example",
    "name": "Ada Obi",
    "email": "ada@acme.com",
    "phone": null,
    "company": "Acme",
    "stage": "LEAD",
    "source": "WEBSITE",
    "form": "Contact page form",
    "message": "Need a quote"
  }
}

Deal moved to Active, create onboarding tasks automatically

When you move a client to the Active stage, your tool adds a welcome task and a note to that client straight away, so onboarding never depends on someone remembering.

Needs: Growth plan or above for the webhook, and Agency Pro or above for the API key.

In eWork Social

  1. Under Webhooks, add your tool address and tick Pipeline stage changed.
  2. Under API keys, press Create key, name it, tick Create and update contacts, and copy the key when it is shown. It appears only once.
Make
  1. Create a scenario with Webhooks, Custom webhook as the trigger. Copy the address into eWork Social and press Send test.
  2. Add a filter on the link between the two modules. The left value is the data field to from the webhook, the operator is Text operators: Equal to, and the right value is the plain text ACTIVE (capitals).
  3. Add the HTTP app, then Make a request. The URL box holds only the address: https://api.eworksocial.com/api/public/v1/clients/ then the clientId field from the webhook, then /tasks. Never paste a curl command into it. Method POST.
  4. Authentication type: No authentication. Open the advanced settings and add two headers: Authorization with the value Bearer then a space then your key, and Content-Type with the value application/json. If you prefer Make API key connection, set the placement to Header and the name to X-API-Key, never to Query string.
  5. Body type Raw, content type JSON, request content: a JSON object with a title, for example a title of Send welcome pack. Any value you insert from the webhook data must sit inside quotes, otherwise Make reports Enter valid JSON in the request body.
  6. Copy the module to add more tasks, or change the URL ending to /notes and send a content field to add a note.
  7. Switch the scenario on.
n8n
  1. Download the starter file below and import it.
  2. Copy the Test URL from the first node into eWork Social under Webhooks and press Send test, then move a test client to Active to see it flow.
  3. In both HTTP Request nodes replace PASTE_YOUR_EWORK_API_KEY with your key. You can store it once as a Header Auth credential instead.
  4. Edit the task title and note text as you like, then switch the workflow to Active and use the Production URL in eWork Social.

Download the n8n file

Zapier
  1. Create a Zap with Webhooks by Zapier, Catch Hook as the trigger. Copy the URL into eWork Social and press Send test.
  2. Add a Filter step: only continue if the data to field exactly matches ACTIVE.
  3. Add the action Webhooks by Zapier, then Custom Request. Method POST. URL: https://api.eworksocial.com/api/public/v1/clients/ followed by the clientId field, then /tasks.
  4. Add the header Authorization with the value Bearer then your key, and Content-Type application/json. Data: a JSON object with a title field.
  5. Publish the Zap.
What the data looks like
{
  "id": "evt_1a2b3c4d5e6f708192a3b4c5",
  "event": "client.stage_changed",
  "workspaceId": "cm0example",
  "createdAt": "2026-11-18T12:05:41.000Z",
  "firedAt": "2026-11-18T12:05:41.000Z",
  "data": {
    "clientId": "cmw0example",
    "name": "Ada Obi",
    "email": "ada@acme.com",
    "company": "Acme",
    "dealValue": 250000,
    "from": "PROPOSAL",
    "to": "ACTIVE"
  }
}

Typeform, Google Forms or any form tool into your CRM

Responses from a form tool that is not on your own website become leads in your CRM, deduplicated by email.

Needs: Growth plan or above. No API key needed.

In eWork Social

  1. Under Website lead capture, press Add form link and copy the address. Treat it like a password: anyone who has it can add leads.
Make
  1. Create a scenario. For the trigger choose your form app: Typeform, Watch Responses, or Google Forms, Watch Responses.
  2. Add the HTTP app, then Make a request. The URL box holds only your form address from eWork Social. Method POST. Authentication type: No authentication, because the private address is the credential.
  3. Body type: application/x-www-form-urlencoded. Add one field per answer with these names: name, email, phone, company, message, and map each from the form response. This avoids the JSON errors that line breaks and quotation marks in answers can cause. Other answers can be added too and are saved in the contact note. Leave the thank-you page empty on the form link when you use Make.
  4. Run once with a real test response. eWork Social replies with ok true and created true for a new person, or created false if that email already exists (a note is added instead).
  5. Switch the scenario on.
n8n
  1. Download the starter file below and import it. It expects a Typeform webhook payload.
  2. Copy the first node Test URL into Typeform under Connect, Webhooks. Submit a test response.
  3. Open the last node and replace PASTE_YOUR_FORM_ADDRESS with your eWork Social form address.
  4. For Google Forms, replace the first node with a Google Sheets Trigger on the sheet linked to your form, and map the columns to name, email, phone, company, message.
  5. Switch the workflow to Active.

Download the n8n file

Zapier
  1. Create a Zap. For the trigger choose Typeform, New Entry. For Google Forms, use Google Sheets, New Spreadsheet Row on the sheet linked to the form.
  2. Add the action Webhooks by Zapier, then POST. URL: your form address from eWork Social. Payload type: json.
  3. Map the data fields: name, email, phone, company, message.
  4. Test the step, then publish the Zap.
What the data looks like
POST <your form address>
Content-Type: application/json

{
  "name": "Ada Obi",
  "email": "ada@acme.com",
  "phone": "+2348000000000",
  "company": "Acme",
  "message": "Interested in the Growth plan",
  "budget": "5000"
}

Response: {"ok":true,"created":true}

Reference

Events you can subscribe to

EventWhen it fires
lead.createdA new contact or lead is added to the CRM, including website form leads.
client.updatedA contact detail changes. The data lists which fields changed and the previous values.
client.stage_changedA contact moves to a different pipeline stage. Includes from and to.
client.deletedA contact is deleted.
note.addedA note is added to a contact.
task.createdA task is created for a contact.
task.completedA task is marked done.
post.publishedA scheduled or instant post went live.
post.failedA post could not be published.
inbox.messageA new comment or direct message arrived in the Engagement Hub.

Every delivery is a JSON message with an id, the event name, your workspace id, a timestamp and a data object. Press Send test next to a webhook in Settings to see a live example in your tool.

API for your automations

Base address: https://api.eworksocial.com/api/public/v1. Send your key in every request as the header Authorization: Bearer ewk_live_your_key. Create keys under Settings, then Integrations, then API keys. A key can be limited to the permissions you tick, can expire, and can be revoked at any time.

MethodPathPermissionWhat it does
GET/meany valid keyConnection test. Returns your workspace and what the key may do.
GET/clientscontacts: readList contacts. Filters: stage, email, updatedSince, limit, cursor.
GET/clients/{id}contacts: readOne contact with recent notes and open tasks.
POST/clientscontacts: writeCreate a contact. Duplicate emails are refused with the existing id.
PATCH/clients/{id}contacts: writeUpdate name, email, phone, company, tags, dealValue, nextFollowUpAt.
POST/clients/{id}/stagecontacts: writeMove to LEAD, CONTACTED, PROPOSAL, ACTIVE or DORMANT.
POST/clients/{id}/notescontacts: writeAdd a note. Body: content.
POST/clients/{id}/taskscontacts: writeAdd a task. Body: title, optional dueDate.
POST/tasks/{id}/completecontacts: writeMark a task done.
GET/accountsposts: readConnected social accounts and their ids (never their tokens).
GET/postsposts: readList posts. Filters: status, limit, cursor.
POST/postsposts: writeCreate a DRAFT or a SCHEDULED post. Immediate publishing is not available.

Quick test from a terminal:

curl https://api.eworksocial.com/api/public/v1/me -H "Authorization: Bearer ewk_live_your_key"

Checking a delivery is genuine

Make, n8n and Zapier do not need this. If you receive webhooks in your own code, verify the signature with the signing secret shown once when you created the webhook.

// Node.js: confirm a delivery really came from eWork Social
const crypto = require('crypto');

function isGenuine(rawBody, signatureHeader, signingSecret) {
  const expected = 'sha256=' + crypto
    .createHmac('sha256', signingSecret)
    .update(rawBody)            // the exact raw text received, not re-serialised
    .digest('hex');
  return signatureHeader === expected;
}

// Headers on every delivery:
//   X-EWork-Event      the event name
//   X-EWork-Delivery   unique id, use it to ignore duplicates
//   X-EWork-Timestamp  when it was sent
//   X-EWork-Signature  sha256=<hmac>

Troubleshooting

Make says: Enter valid JSON in the request body

A value inserted from your form or webhook is outside quotation marks, or contains a line break. Use the form-urlencoded body type instead of Raw JSON (see the form template), or put each inserted value inside quotes.

Slack says: channel_not_found

Pick the channel from the list instead of typing it. Channel names are lowercase with dashes, no spaces. Invite the Make app to the channel, and for a private channel use its channel ID.

HTTP says: Not Found

The URL box must contain only the web address. If a curl command or a header was pasted into it, the address becomes invalid. Check the base address ends with /api/public/v1 and the path matches the reference above.

HTTP says 401 Unauthorized

The key is missing, wrong or sent in the wrong place. Send it in a header: Authorization with the value Bearer then your key, or X-API-Key with the key alone. Never put it in the query string.

HTTP says 403 Forbidden

The key is valid but not allowed to do that. Create a key with the right permission ticked, or check the workspace is on Agency Pro or above.

HTTP says 409 for a new contact

A contact with that email already exists. This is expected. The reply includes the existing contact id so you can update it instead.

My filter lets nothing through

Compare the webhook field to plain text. For example the data field to equals the text ACTIVE, in capitals. Comparing two data fields to each other will never match.

Name and email are empty in my test

The Send test button sends a sample message with no contact details. Trigger a real event, such as adding a lead or moving a client, to see real data.

Common questions

Do I need to write code?

No. Make, n8n and Zapier are point-and-click tools. The templates below tell you which boxes to fill in. Code samples are there for developers who want them.

Is there a native eWork Social app inside Make or Zapier?

Not yet. You connect with their standard webhook and HTTP steps, which work the same way and are covered by the templates here.

What happens if my tool is down when an event fires?

Today each event is sent once, with a ten second timeout, and the last result is shown next to the webhook in Settings. Automatic retries are planned.

Is it safe?

Keys are stored only as a one-way hash, so even we cannot read them back. Each key has permissions you choose, can expire, and can be revoked instantly. Webhook addresses must be public https addresses, and every delivery is signed so you can verify it.

Are there limits?

Each API key allows 120 requests per minute (higher on Enterprise). A workspace can have up to 10 webhooks, 10 active API keys and 5 form links.

Ready to connect your tools?

Webhooks and lead capture start on the Growth plan. API keys are included with Agency Pro and above.

See plansStart free