ChirplyA practical example
An integration looks up the current action schema, supplies a scoped credential and sends the required input for one supported operation. It checks the returned result and stores enough information to retry safely if the request outcome is uncertain.
How to use this concept
Read the operation's current schema instead of inferring field names from a screen. Confirm which account the credential acts within and whether the caller has the required permission. Use a controlled record for the first request.
Separate read operations from operations that create effects. Sending a message can contact a real person and incur provider usage, while deleting a record can remove data. Review the action description, risk classification and costs before executing it.
Handle errors and pagination according to the documented contract. Keep credentials on the server, record a correlation identifier where available and make retry behavior explicit. Verify the resulting CRM state as part of an integration test, particularly after a timeout.
How do Chirply's API, MCP and Copilot relate?
Chirply's capability registry defines supported operations once and exposes them through REST, MCP and the built-in Copilot. The current action catalog supplies operation descriptions and input schemas. Authentication, permissions and confirmation behavior depend on the calling surface.