Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

KrispCall

KrispCall is a cloud telephony system for modern businesses, offering advanced features for high-growth startups and modern enterprises.

CategoryCommunication
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect KrispCall with Flows360

KrispCall is a cloud telephony system for modern businesses, offering advanced features for high-growth startups and modern enterprises.

Use the KrispCall connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 5 triggers.

Available actions

  • Add Contact
  • Delete Contacts
  • Send SMS
  • Send MMS

Available triggers

  • New Voicemail
  • New MMS/SMS
  • New Contact
  • New Call Log
  • Outbound MMS/SMS

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: KrispCall
  • Package: @activepieces/piece-krisp-call@0.1.6
  • Exact artifact digest: sha256:d4110a38573cf5334971dd35daa288958d0ae608dd4108a9a3e03cfd4746a58a
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Contact (addContact), Add contact in Krispcall Classification: read.
  • Delete Contacts (deleteContacts), Delete contacts from krispcall. Classification: read.
  • Send SMS (sendSms), Send sms in Krispcall. Classification: read.
  • Send MMS (sendMms), Send mms in krispcall. Classification: read.

Trigger contracts

  • New Voicemail, webhook.
  • New MMS/SMS, webhook.
  • New Contact, webhook.
  • New Call Log, webhook.
  • Outbound MMS/SMS, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions4
Triggers5

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Contact Yes No Add contact in Krispcall
Delete Contacts Yes No Delete contacts from krispcall.
Send SMS Yes No Send sms in Krispcall.
Send MMS Yes No Send mms in krispcall.
New Voicemail Yes No webhook trigger declared by the pinned package.
New MMS/SMS Yes No webhook trigger declared by the pinned package.
New Contact Yes No webhook trigger declared by the pinned package.
New Call Log Yes No webhook trigger declared by the pinned package.
Outbound MMS/SMS Yes No webhook trigger declared by the pinned package.

Supported actions

Add Contact · Read

Add contact in Krispcall

add_contact · Risk: low · Retry: safe

Inputs

  • name · string · Optional, Enter your name
  • number · string · Required, Enter contact number
  • address · string · Optional, Enter your address
  • company · string · Optional, Enter your company
  • email · string · Optional, Enter your email
Delete Contacts · Read

Delete contacts from krispcall.

delete_contacts · Risk: low · Retry: safe

Inputs

  • contacts · array · Optional, Enter contact which you want to delete.
Send SMS · Read

Send sms in Krispcall.

send_sms · Risk: low · Retry: safe

Inputs

  • from_number · string · Required, Select an Number
  • to_number · string · Required, Enter the number to which you want to send sms.
  • content · string · Required, Enter your message here.
Send MMS · Read

Send mms in krispcall.

send_mms · Risk: low · Retry: safe

Inputs

  • from_number · string · Required, Select an number
  • to_number · string · Required, Enter the number to which you want to send sms.
  • content · string · Optional, Enter your message here.
  • medias · array · Required, Enter medias urls

Triggers

New Voicemail · Webhook

Trigger when a new voicemail is received.

New MMS/SMS · Webhook

Trigger when a new MMS/SMS is received.

New Contact · Webhook

Trigger when a new contact is added.

New Call Log · Webhook

Trigger when a new call log is recorded.

Outbound MMS/SMS · Webhook

Trigger when a new MMS/SMS is sent.

Setup

Setup

  1. Add the KrispCall connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • API key (apiKey), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-krisp-call@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required KrispCall connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-krisp-call@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com