QuiQSol on Zapier

The QuiQSol app on Zapier links your CRM to the rest of your stack. Triggers are instant: Zapier hears about a new lead or a won deal the second it happens in QuiQSol, with no polling delay.

Triggers

• New Lead: a new lead lands in the CRM, with its source, channel, ad platform and campaign.
• Lead Qualified: a lead is marked Qualified.
• Deal Won: a deal moves to a won stage, with its value.
• New Form Response: someone submits a Quiq Form, with every answer.

Actions

• Create or Update Lead: adds a lead, or updates the one with the same email.
• Create or Update Contact: adds a contact, or updates the one with the same email.

1. Create an API key

1. In QuiQSol open Settings → Developer Platform.
2. Click Create API key, name it "Zapier" and copy the key. It is shown once.

The key belongs to your workspace. Anyone holding it can add leads and receive CRM events, so keep it in Zapier only. Revoke it from the same page at any time; every Zap using it stops at once.

2. Connect QuiQSol in Zapier

1. In Zapier, create a Zap and search for QuiQSol.
2. Pick a trigger or an action, then click Sign in.
3. Paste the API key. Zapier shows the connection under your workspace name.

3. Build your first Zap

Send won deals to a spreadsheet: trigger QuiQSol: Deal Won, action Google Sheets: Create Spreadsheet Row. Map deal title, amount, company and closed date.

Add website or ad leads to the CRM: trigger from your form or ad tool, action QuiQSol: Create or Update Lead. Map first name, last name, email, phone and company. A lead with the same email is updated, never duplicated.

Alert the team in Slack on a qualified lead: trigger QuiQSol: Lead Qualified, action Slack: Send Channel Message.

While you build, Zapier loads your latest real records as samples. A new workspace sees example data until its first lead arrives.

4. Send CRM results to LinkedIn as conversions

Teach LinkedIn which ad clicks became pipeline and revenue, so your campaigns optimise on real results.

The fastest route needs no Zapier: open CRM → LinkedIn Ads, connect your ad account and choose which CRM events count as which conversion. QuiQSol sends them through the LinkedIn Conversions API, hashed, logged and retried.

To run it through Zapier instead:

1. In Campaign Manager, create a conversion under Analyze → Conversion tracking and pick Zapier as the data source.
2. In Zapier, trigger QuiQSol: Lead Qualified or QuiQSol: Deal Won.
3. Action LinkedIn Conversions: Send Conversion Event. Choose the ad account and the conversion.
4. Map Email to the QuiQSol email field and the event time to createdAt (leads) or closedAt (deals). For Deal Won, map amount to the conversion value and set your currency.
5. Test the step and turn the Zap on. LinkedIn Conversions steps do not use Zapier tasks.

LinkedIn matches people by email, so leads without an email are skipped.

5. Manage and monitor

• Every delivery to Zapier is logged in QuiQSol under CRM → LinkedIn Ads → Sent events, and retried with backoff if Zapier does not answer.
• Turning a Zap off removes its subscription in QuiQSol automatically.
• A workspace can run up to 100 QuiQSol trigger Zaps at once.

API reference

The Zapier app uses the QuiQSol public API at https://api.quiqsol.com/public/v1/zapier. Every request sends the API key as Authorization: Bearer <key>, over HTTPS only.

• GET /me: Connection test. Returns workspace, subdomain and keyName.
• POST /hooks: Subscribe. Body { "event", "targetUrl" }; event is lead.created, lead.qualified, deal.won or form.submitted; targetUrl must be https. Returns { "id", "event" }.
• DELETE /hooks/{id}: Unsubscribe.
• GET /samples/{event}: Up to three recent records for the event, in the same shape as a live delivery.
• POST /leads: Create or update a lead. Body: firstName (required), lastName, email, phone, jobTitle, company. Returns 201 when created, 200 when updated.
• POST /contacts: Create or update a contact. Same fields without company. Needs a key with contacts write access.

A delivery to Zapier carries id, event, firstName, lastName, email, phone, company, jobTitle, source, channel, adPlatform, campaign and url, plus status, qualified and createdAt for leads, dealTitle, amount, stage and closedAt for deals, and formId, answers and submittedAt for form responses.

Errors return a JSON error message: 400 for invalid input, 401 for a missing or revoked key, 429 when the rate limit is reached. The rest of the public API (contacts, tickets, leads) is described at api.quiqsol.com/openapi.json.