Connect Zapier

Zapier joins DealJourney to thousands of other tools without code. A Zap watches for something happening in one tool and does something in another. "When a deal is won, post it in Slack." "When a form is submitted, create a lead".

Get your key

An administrator does this once.

1. 1Open Markedsplads from the sidebar and find Zapier.
2. 2Choose Opret Zapier-nøgle.
3. 3Copy the key. It is shown once. If you lose it, come back and create another rather than hunting for the old one.

The permissions are set for you, including the webhook ones triggers depend on. Getting those wrong is the usual reason a Zap connects fine and then never fires, which is why this is one button rather than a list of tick boxes.

If your plan does not include a module, the key is simply created without it and the page says which parts are missing. You can also build a key by hand under API-nøgler, but there is rarely a reason to.

An account can have two API keys at a time. If you already have two, the page will say so and point you at the list to revoke one you no longer use.

Connect the account in Zapier

1. 1In Zapier, add a step and search for DealJourney.
2. 2Choose Sign in and paste the key.
3. 3Leave the API Base URL exactly as it is. It only exists so our support team can point a test at a sandbox.

The connection is then named after your company, so if you connect more than one account you can tell them apart.

What Zapier can watch for

Triggers fire within seconds of the change, because DealJourney pushes to Zapier rather than Zapier checking every few minutes.

• Leads, customers and contacts: created, changed, deleted.
• Opportunities: created, changed, moved to another stage, won, lost, deleted. The stage-change trigger tells you which stage the deal came from, which is what lets you react only to the move you care about.
• Activities: created, changed, completed, deleted.
• Documents out for signature: sent, opened by a signer, signed by one party, fully completed, declined, or a change requested. "Signed" fires each time a party signs; wait for "completed" if you need everyone.

For privacy, a document trigger tells you *that* a document was signed and which record it belongs to. It never sends the document's contents.

What Zapier can do in DealJourney

• Create leads, customers, contacts, opportunities, activities and notes.
• Update a customer, or move an opportunity to another stage.
• Mark an opportunity won, which can also create the customer, subscription and invoice that follow from it.
• Convert a lead into a customer and contact.
• Find a customer, contact, lead or opportunity.

Use "Find or create" rather than plain "Create" whenever the record might already exist. A Zap that only creates will happily make a second copy of the same company every time it runs, and cleaning that up afterwards takes far longer than setting it up correctly. Match on organisation number for companies and on email for people. Names are spelt too many ways to match on.

When something is not working

The trigger never fires. Almost always the key is missing webhook permission, which is what Opret Zapier-nøgle avoids. Fix the key, then switch the Zap off and on again so it re-subscribes.

Zapier says permission denied. The key is valid but lacks permission for that specific record type, so reconnecting with the same key will not help. Add the missing permission to the key; Zapier's error message names it.

Records stop arriving after a while. If your endpoint fails repeatedly DealJourney gives up on it, so check the Zap is switched on and has not errored.

Test with one record first. Run the Zap once, look at what arrived on both sides, then let it loose. A Zap pointed at the wrong field does not make one mistake, it makes thousands.

Turning it off

Switching a Zap off removes its subscription, so DealJourney stops sending. What already reached the other tool stays where it is. To cut everything off at once, revoke the API key. That stops every Zap using it immediately.