How do I install the Sinch API Webhooks Triggers skill?

Run npx skillmds@latest add sinch/sinch-api-webhooks-triggers in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Sinch API Webhooks Triggers skill do?

Show available webhook trigger types for Sinch Conversation API It is listed under Integrations & APIs on SkillMD.

Is Sinch API Webhooks Triggers safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sinch API Webhooks Triggers?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sinch API Webhooks Triggers free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sinch API Webhooks Triggers?

sinch (@sinch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sinch API Webhooks Triggers by sinch

Name: Sinch API Webhooks Triggers
Rating: 4.5 (4 reviews)
Author: sinch

File contents

Webhook Triggers Reference

Display all available webhook trigger types for the Sinch Conversation API. Use this as a reference when creating or updating webhooks.

IMPORTANT: Execute this command directly. Do NOT generate script files. Simply display the trigger list below.

Input

No arguments required

Arguments: $ARGUMENTS

Instructions

Display the information directly - do not write code or scripts:

Display the complete list of available webhook triggers with descriptions:

Message Events

MESSAGE_DELIVERY - Fired when a message is delivered to the recipient
MESSAGE_INBOUND - Fired when an inbound message is received from a contact
MESSAGE_SUBMIT - Fired when a message is submitted for sending
MESSAGE_INBOUND_SMART_CONVERSATION_REDACTION - Fired for smart conversation redaction events

Conversation Events

CONVERSATION_START - Fired when a new conversation is started
CONVERSATION_STOP - Fired when a conversation is stopped
CONVERSATION_DELETE - Fired when a conversation is deleted

Contact Events

CONTACT_CREATE - Fired when a new contact is created
CONTACT_DELETE - Fired when a contact is deleted
CONTACT_MERGE - Fired when contacts are merged
CONTACT_UPDATE - Fired when a contact is updated

Opt-In/Opt-Out Events

OPT_IN - Fired when a contact opts in for messages
OPT_OUT - Fired when a contact opts out from messages

Capability Events

CAPABILITY - Fired when channel capability information is updated

Channel Events

CHANNEL_EVENT - Fired for various channel-specific events

Unsupported Events

UNSUPPORTED - Fired for unsupported or unknown event types

Provide usage examples for common trigger combinations
Link to official documentation for more details

Examples

View all available triggers:

/sinch-api-webhooks-triggers

Common Trigger Combinations

Basic messaging webhook (most common):

MESSAGE_DELIVERY,MESSAGE_INBOUND

Full message lifecycle tracking:

MESSAGE_SUBMIT,MESSAGE_DELIVERY,MESSAGE_INBOUND

Conversation management:

CONVERSATION_START,CONVERSATION_STOP,MESSAGE_INBOUND,MESSAGE_DELIVERY

Opt-in/Opt-out management:

OPT_IN,OPT_OUT,MESSAGE_INBOUND

Comprehensive monitoring:

MESSAGE_DELIVERY,MESSAGE_INBOUND,MESSAGE_SUBMIT,CONVERSATION_START,CONVERSATION_STOP,OPT_IN,OPT_OUT

API Reference

Documentation: https://developers.sinch.com/docs/conversation/api-reference/conversation/tag/Webhooks/
Webhook Events: https://developers.sinch.com/docs/conversation/webhooks/

Notes

You can configure multiple triggers for a single webhook
Not all channels support all event types
Choose only the triggers you need to reduce unnecessary webhook traffic
MESSAGE_DELIVERY and MESSAGE_INBOUND are the most commonly used triggers
Use CONVERSATION_START and CONVERSATION_STOP for conversation lifecycle tracking

---name: sinch-api-webhooks-triggersdescription: Show available webhook trigger types for Sinch Conversation API---# Webhook Triggers ReferenceDisplay all available webhook trigger types for the Sinch Conversation API. Use this as a reference when creating or updating webhooks.**IMPORTANT: Execute this command directly. Do NOT generate script files. Simply display the trigger list below.**## InputNo arguments requiredArguments: $ARGUMENTS## Instructions**Display the information directly - do not write code or scripts:**1. Display the complete list of available webhook triggers with descriptions:### Message Events- `MESSAGE_DELIVERY` - Fired when a message is delivered to the recipient- `MESSAGE_INBOUND` - Fired when an inbound message is received from a contact- `MESSAGE_SUBMIT` - Fired when a message is submitted for sending- `MESSAGE_INBOUND_SMART_CONVERSATION_REDACTION` - Fired for smart conversation redaction events### Conversation Events - `CONVERSATION_START` - Fired when a new conversation is started- `CONVERSATION_STOP` - Fired when a conversation is stopped- `CONVERSATION_DELETE` - Fired when a conversation is deleted### Contact Events- `CONTACT_CREATE` - Fired when a new contact is created- `CONTACT_DELETE` - Fired when a contact is deleted- `CONTACT_MERGE` - Fired when contacts are merged- `CONTACT_UPDATE` - Fired when a contact is updated### Opt-In/Opt-Out Events- `OPT_IN` - Fired when a contact opts in for messages- `OPT_OUT` - Fired when a contact opts out from messages### Capability Events- `CAPABILITY` - Fired when channel capability information is updated### Channel Events- `CHANNEL_EVENT` - Fired for various channel-specific events### Unsupported Events- `UNSUPPORTED` - Fired for unsupported or unknown event types2. Provide usage examples for common trigger combinations3. Link to official documentation for more details## ExamplesView all available triggers:```/sinch-api-webhooks-triggers```## Common Trigger Combinations**Basic messaging webhook** (most common):```MESSAGE_DELIVERY,MESSAGE_INBOUND```**Full message lifecycle tracking**:```MESSAGE_SUBMIT,MESSAGE_DELIVERY,MESSAGE_INBOUND```**Conversation management**:```CONVERSATION_START,CONVERSATION_STOP,MESSAGE_INBOUND,MESSAGE_DELIVERY```**Opt-in/Opt-out management**:```OPT_IN,OPT_OUT,MESSAGE_INBOUND```**Comprehensive monitoring**:```MESSAGE_DELIVERY,MESSAGE_INBOUND,MESSAGE_SUBMIT,CONVERSATION_START,CONVERSATION_STOP,OPT_IN,OPT_OUT```## API Reference- **Documentation**: https://developers.sinch.com/docs/conversation/api-reference/conversation/tag/Webhooks/- **Webhook Events**: https://developers.sinch.com/docs/conversation/webhooks/## Notes- You can configure multiple triggers for a single webhook- Not all channels support all event types- Choose only the triggers you need to reduce unnecessary webhook traffic- `MESSAGE_DELIVERY` and `MESSAGE_INBOUND` are the most commonly used triggers- Use `CONVERSATION_START` and `CONVERSATION_STOP` for conversation lifecycle tracking

Frequently asked questions

Sinch API Webhooks Triggers