Concept:
Workflows
can interact with external software systems (that are not directly integrated in the Settings
menu) using Webhooks
. A webhook is essentially a way for applications to send automated messages or data to each other when something happens.
- Sending Data OUT (
Webhook
Action):- Purpose: Send information from
Close Master
to another system when a workflow step is reached. - Action: Add the
Webhook
orCustom Webhook
action in your workflow. - Configuration: You need the unique Webhook
URL
provided by the receiving external system (e.g., a URL from Zapier, Make.com, a custom reporting tool, or another CRM). You then configure the data payload (often inJSON
format) thatClose Master
should send, typically usingCustom Values
and contact/opportunity fields to dynamically populate the data sent (e.g., sendcontact.name
,contact.email
,opportunity.stage
to the external URL).
- Purpose: Send information from
- Receiving Data IN (
Inbound Webhook
Trigger):- Purpose: Start a
Close Master
Workflow
when an external system sends data toClose Master
. - Trigger: Use the
Inbound Webhook
trigger type when creating a workflow. - Configuration:
Close Master
provides a uniqueURL
for this trigger. You need to configure the external system to send data (usually via anHTTP POST
request inJSON
format) to this specificURL
whenever the relevant event occurs in that external system. The data sent can then be used as merge fields within the triggered workflow (e.g.,{{trigger.data.fieldName}}
).
- Purpose: Start a
Setup Responsibility:
Configuring webhooks requires technical understanding of APIs
, data formats (JSON
), and the specific requirements of both sending and receiving systems. This setup is typically handled by The Close Agency
administrators or requires advanced technical expertise. As an end-user, you generally wouldn't configure these yourself, but it's useful to understand the concept if your agency uses webhooks for integrations (like connecting certain lead sources or syncing data with other platforms).