%20(3).png)
Zid
Customers, products and orders
Connect Zid store records to contacts and service workflows.
INTEGRATIONS
Your systems. One connected customer story.
Connect business data to the conversation in UCaaS. Bring orders, customer records and service updates into a defined flow—so your team can act with the details in view.
ORDER / 1048
The detail starts here.
Customer
Nawaf
Order status
Confirmed
Source
Online store
A useful update
Ready for follow-up
UCaaS
Customer context
N
Nawaf
Order #1048
Linked order
Confirmed · delivery next
Great, I have your order details. Let’s confirm the next step.
Conversation + customer + order
01
Business connectors
Connect selected records through a defined provider integration.
02
Event-driven webhooks
Let a record change trigger the next connected action.
03
APIs for developers
Build an agreed connection around documented operations.
BUSINESS CONNECTIONS
Start with the systems your team already uses.
Connect the records and actions that matter to your customer journey.
Salla
Customers, products and orders
Connect store records to contacts and service workflows.
Zoho
Leads, contacts and tickets
Connect updates and defined write-back to Zoho CRM.
Foodics
Order updates and invoices
Share supported order statuses and invoice details.
Zendesk
Contacts and service tickets
Keep supported ticket updates connected to the work.
Trello
Boards, lists and cards
Connect card work, comments, labels and attachments.
Asana
Projects, tasks and subtasks
Connect task progress, comments and project updates.
Connector availability and the supported operations are confirmed for your account before activation. Provider access, subscription and API permissions may be required.
COMMERCE & CUSTOMER EXPERIENCE
The order belongs in the follow-up, too.
Connect customer, product and order records from Salla and Zid to the defined UCaaS records and workflows. Foodics adds supported order-status notifications and invoice information, subject to the provider’s APIs.
Order-to-service journey
Example
01
Order received
Customer and order data
02
Event recognised
A configured workflow starts
03
Team informed
Follow-up with the context
1048
“I can see the order. What would you like to update?”
The team starts with a reference, not a repeated question.
Connect order notifications with the customer’s conversation and follow-up.
CRM & SALES DATA
Reply with the relationship in view.
Connect Zoho leads, contacts and tickets. Use supported events to start follow-up and write agreed updates back to Zoho CRM, with a clear direction for each field.
Customer record
Linked context
Customer
Nawaf
Related order
#1048
Follow-up
Confirm delivery
Team note
The customer requested an updated delivery time.
Defined write-back
Keep the agreed fields in step.
UCaaS ↔ CRM
SERVICE & PROJECT WORK
Let the request reach the people who can finish it.
Connect Zendesk contacts and ticket updates. For project work, Trello connects boards, lists and cards; Asana connects projects, tasks and subtasks. Carry supported comments and updates through the agreed workflow.
SERVICE / 2048
Review the delivery change
Customer
Nawaf
Owner
Service team
Coordinate with operations
Comment · status · next action
“The request is clear. I’ll confirm the timing with the team.”
FIELD MAPPING
Same customer. Consistent meaning across systems.
Map the fields and updates that keep customer records connected across systems.
Field mapping
Source system
UCaaS record
Type
Customer name
Contact name
Text
Mobile number
Contact phone
Phone
Order reference
Linked order ID
Identifier
Order status
Follow-up context
Status
Review before activation
Agree the fields, direction and update behaviour.
WEBHOOKS
When a record changes, the connection has a reason to act.
Manage webhooks for record creation, updates and deletion across tickets, contacts and accounts. Define the destination and purpose of the connection so data exchange follows the work your team actually handles.
Webhook registry
Admin workspace
Tickets
Create · update · delete
Contacts
Create · update · delete
Accounts
Create · update · delete
A named connection with a defined event.
Manage the webhook list and maintain the configured connections.
ADVANCED WEBHOOKS & ZAPIER
Choose the event. Shape the payload. Follow the delivery.
Use APIs and webhooks to connect business events with customer communication and follow-up.
Outbound event delivery
Connected workflows
Event
Ticket updated
Destination
Connected workflow
PAYLOAD / SAMPLE
{ "event": "ticket.updated", "record": "2048", "status": "open" }Attempt 01
Retry scheduled
Attempt 02
Delivered
Connect the event and its data to the next action.
IN-PLATFORM API DOCUMENTATION
Give developers a clear starting point.
Connect systems through APIs with clear record mapping and authorised access.
Developer workspace
API documentation
Modules
Contacts
Tickets
Messages
Understand → test → connect
cURL
Node.js
Python
REQUEST HEADERS
Authorization: Bearer <access_token> Accept: application/json
Use the documented request and response structure.
Access
Authorised role
Test history
Review the response
ACCESS & TRACEABILITY
A connection needs control as well as a destination.
Agree who can configure the connection, which data it uses and how the team will review its execution.
01
Authorise the right connection
OAuth 2.0, provider tokens or API keys are used according to the connector. Confirm the required permissions before connecting.
02
Keep account access defined
Organise connection access around roles and the systems involved.
03
Keep a trace of execution
Advanced audit, delivery and test logs help the team investigate a failed exchange and review the next action.
A useful integration starts with an agreed brief.
1
Define the outcome
Choose the customer journey, records and expected action.
2
Confirm the connection
Check availability, provider access and supported fields.
3
Test with sample records
Review mapping, event behaviour and handling of failures.
4
Activate and review
Assign ownership and agree how changes will be maintained.
Need a broader connection?
Build business connections around the records, events and follow-up your team needs.
Before you connect your next system.
Are all listed connectors active in every account?
No. Availability, supported operations, provider permissions and any required add-on are confirmed before activation. A listed connector does not imply automatic access in your account.
How is a connector different from a webhook or API?
A connector defines an integration with a specific system. A webhook sends an event to a configured destination. APIs let a developer request or change supported data through documented operations.
Is every sync bidirectional and instant?
No. Direction, events, update timing and supported fields depend on the connector and provider APIs. Agree these details for the actual use case.
Can an external event start a UCaaS workflow?
Connect external events to customer records, conversations and follow-up workflows.
Does the connection include a full data migration?
Plan data migration, field mapping and connection costs around the information your business needs.
Where can our developers explore the APIs?
Use API documentation and authorised testing to understand the records and actions in your connection.
Which system should your next conversation connect to?
Connect your systems to the customer journey.