Authenticate using your Contacts API credentials to authorize the EZ Texting app connector. Use your API key or OAuth token for secure access and perform a quick lookup to verify connectivity.
In this step, grant EZ Texting permission to access and push data to your Contacts API account. Approve the requested scopes and test the connection.
GET /contacts/:contactId; GET /contacts/:contactId/tasks; GET /contacts/:contactId/tasks/:taskId; GET /contacts/:contactId/notes; GET /contacts/:contactId/notes/:id; GET /contacts/:contactId/appointments; GET /contacts/; GET /contacts/business/:businessId; POST /contacts/; PUT /contacts/:contactId; DELETE /contacts/:contactId; POST /contacts/:contactId/tasks; PUT /contacts/:contactId/tasks/:taskId; PUT /contacts/:contactId/tasks/:taskId/completed; DELETE /contacts/:contactId/tasks/:taskId; POST /contacts/:contactId/tags
Trigger: a contact is updated in EZ Texting or a lookup is needed, prompting a call to GET /contacts/:contactId.
Actions: Retrieve contact (GET /contacts/:contactId), fetch tasks (GET /contacts/:contactId/tasks) and notes (GET /contacts/:contactId/notes) to surface up-to-date context in EZ Texting.
GET /contacts/:contactId
contactId, taskId, notesId
Trigger: new or updated contact created in EZ Texting
Actions: POST /contacts/ to create and PUT /contacts/:contactId to update, mapping fields like name, email, and phone
POST /contacts/; PUT /contacts/:contactId
name, email, phone, businessId
Trigger: a task is created, updated, or completed in Contacts API to drive EZ Texting actions
Actions: POST /contacts/:contactId/tasks, PUT /contacts/:contactId/tasks/:taskId, PUT /contacts/:contactId/tasks/:taskId/completed
POST /contacts/:contactId/tasks; PUT /contacts/:contactId/tasks/:taskId; PUT /contacts/:contactId/tasks/:taskId/completed
contactId, taskId
Automate data flow without writing code, reducing manual entry and errors
Centralize SMS campaigns and contact data in a single workflow for faster campaigns
Go from lead to message quickly with reliable, event-driven automation
This glossary explains core concepts used when connecting the Contacts API to EZ Texting, including endpoints, triggers, actions, fields and methods.
Application Programming Interface that allows software to communicate and exchange data securely.
A specific URL in an API that performs a function, such as retrieving a contact or their tasks.
An event that starts an automation, like a contact update or new contact creation.
An operation executed by an automation, such as creating or updating a contact or sending a message.
Trigger a welcome SMS when a new contact is added, using EZ Texting.
Send reminder messages when a task is due, using the Contacts API task data.
After support, trigger a satisfaction survey via EZ Texting.
Obtain your EZ Texting API key and add it to the connector settings.
Match contact fields (name, phone, email) to EZ Texting data points and select endpoints.
Run test messages, verify data flow, then enable automation in your workspace.
The integration connects EZ Texting with the Contacts API to automate SMS workflows without writing code. You can read contact data, pull related items like tasks and notes, and trigger messages based on contact events. This keeps your communications timely and consistent. No-code automation lets you map fields and endpoints to drive your campaigns.
Coding is not required for the basic setup. The connectors provide a no-code interface to authenticate, map fields, and configure triggers and actions. For advanced custom logic, you can extend with conditional actions or webhooks.
At minimum, you’ll use GET /contacts/:contactId to retrieve a contact. For richer workflows, include GET /contacts/:contactId/tasks and GET /contacts/:contactId/notes to surface context, plus POST /contacts/ and PUT /contacts/:contactId for create/update operations.
Yes. You can create new contacts with POST /contacts/ and update existing ones with PUT /contacts/:contactId. You can also attach tasks and tags via POST /contacts/:contactId/tasks and POST /contacts/:contactId/tags.
Security is handled via standard API authentication (keys or OAuth) and secure data transmission. Scopes and permissions should be limited to what your automation requires. Rotate credentials regularly and monitor access logs.
If you need more than the three suggested steps, you can add additional steps to the automation to cover speech, campaigns, or custom data flows. The no-code builder supports multiple sequential actions and branching.
Logs and errors can be viewed in the app connector’s dashboard. You can review request payloads, response codes, and timestamped events to troubleshoot and refine mappings.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
