Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

OpenMic AI

An AI-powered platform that automates phone calls using advanced language models.

CategoryCommunication
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect OpenMic AI with Flows360

An AI-powered platform that automates phone calls using advanced language models.

Use the OpenMic AI 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 6 actions and 1 trigger.

Available actions

  • Create Phone Call
  • Find Bot
  • Find Call
  • Get Bots
  • Get Calls
  • Custom API Call

Available triggers

  • New Post-call Summary

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: OpenMic AI
  • Package: @activepieces/piece-openmic-ai@0.2.0
  • Exact artifact digest: sha256:cc814ce159da4ce8b738f9af01f0809772172291064927f73ee40fd07cd52aa8
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Create Phone Call (createPhoneCall), Create a new outbound phone call using OpenMic AI Classification: read.
  • Find Bot (findBot), Retrieve details of a specific bot by its UID Classification: read.
  • Find Call (findCall), Retrieve details of a specific call by its ID Classification: read.
  • Get Bots (getBots), Retrieve all bots with optional filtering and pagination Classification: read.
  • Get Calls (getCalls), Retrieve all calls with optional filtering and pagination Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Post-call Summary, 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 objects7
Supported actions6
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Openmic AI API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Phone Call Yes No Create a new outbound phone call using OpenMic AI
Find Bot Yes No Retrieve details of a specific bot by its UID
Find Call Yes No Retrieve details of a specific call by its ID
Get Bots Yes No Retrieve all bots with optional filtering and pagination
Get Calls Yes No Retrieve all calls with optional filtering and pagination
Custom API Call Yes No Make a custom API call to a specific endpoint
New Post-call Summary Yes No webhook trigger declared by the pinned package.

Supported actions

Create Phone Call · Read

Create a new outbound phone call using OpenMic AI

create_phone_call · Risk: low · Retry: safe

Inputs

  • fromNumber · string · Required, The number you own in E.164 format (e.g., +1234567890)
  • toNumber · string · Required, The number you want to call in E.164 format (e.g., +0987654321)
  • overrideAgentId · string · Optional, The bot UID to override the default agent
  • customerId · string · Optional, Customer identifier for tracking
  • dynamicVariables · object · Optional, Key-value pairs to replace in the prompt
  • callbackUrl · string · Optional, Callback URL to receive call events
Find Bot · Read

Retrieve details of a specific bot by its UID

find_bot · Risk: low · Retry: safe

Inputs

  • uid · string · Required, The unique identifier of the bot
Find Call · Read

Retrieve details of a specific call by its ID

find_call · Risk: low · Retry: safe

Inputs

  • callId · string · Required, The unique identifier of the call
Get Bots · Read

Retrieve all bots with optional filtering and pagination

get_bots · Risk: low · Retry: safe

Inputs

  • name · string · Optional, Filter by bot name (partial match)
  • createdAfter · string · Optional, Filter bots created after this date (ISO 8601 format)
  • createdBefore · string · Optional, Filter bots created before this date (ISO 8601 format)
  • limit · number · Optional, Maximum number of bots to return (1-100)
  • offset · number · Optional, Number of bots to skip for pagination
Get Calls · Read

Retrieve all calls with optional filtering and pagination

get_calls · Risk: low · Retry: safe

Inputs

  • customerId · string · Optional, Filter by customer ID
  • fromNumber · string · Optional, Filter by originating phone number
  • toNumber · string · Optional, Filter by destination phone number
  • botId · string · Optional, Filter by bot ID
  • fromDate · string · Optional, Filter calls from this date (ISO 8601 format)
  • toDate · string · Optional, Filter calls to this date (ISO 8601 format)
  • callStatus · string · Optional, Filter by call status
  • callType · string · Optional, Filter by call type
  • limit · number · Optional, Maximum number of calls to return (1-100)
  • offset · number · Optional, Number of calls to skip for pagination
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Post-call Summary · Webhook

Trigger when a new call completes with comprehensive call data and analysis

Inputs

  • markdown · string

Setup

Setup

  1. Add the OpenMic AI 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:
  • No provider credential fields are declared by the pinned package.
  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-openmic-ai@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 1 trigger 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 OpenMic AI 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-openmic-ai@0.2.0 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