Communication services from Microsoft Azure
Azure Communication Services currently provides 1 action a workflow can run. Use those building blocks to route important conversations into accountable work without copying context by hand.
Send Email
Send a text or HTML email
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Use a change in Coherence to run a supported Azure Communication Services action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Send Email
Combine Azure Communication Services with another integration and Coherence records to route important conversations into accountable work without copying context by hand.
Starts with
A Coherence workflow starts
Finishes with
Send Email, then preserve the outcome in Coherence
The exact authentication fields depend on Azure Communication Services. The workflow structure stays straightforward:
Authorize the Azure Communication Services account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Azure Communication Services or provide a complementary trigger or action.
Azure Communication Services currently provides 1 action a workflow can run. Use those building blocks to route important conversations into accountable work without copying context by hand.
Azure Communication Services currently lists 0 triggers and 1 action in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Azure Communication Services triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
