App Type value for Custom Call Recorder integrations

When configuring a Custom Call Recorder integration to send calls into Pylon, you may be asked for an App Type value. This field identifies the integration as a Custom Call Recorder so that Pylon ingests it correctly.

Required App Type value

For all Custom Call Recorder setups, including Zapier-based flows, set the App Type field to:

custom_call_recorder

This value is required whenever you are using the Custom Call Recorder path to send calls into Pylon, for example:

• Zapier automations that forward call recordings from third-party tools (such as generic or unsupported call recorders) into Pylon.

• Other custom integrations that use the Custom Call Recorder ingestion route.

How this maps to the UI

Some setup flows label this field as App Type in the UI, but expect the internal identifier custom_call_recorder as the value. These are the same thing:

Provider and ingestion path coverage

Use custom_call_recorder for all integrations that rely on Pylon's Custom Call Recorder path, regardless of:

• The call recording provider.

• Whether you connect via Zapier, another automation tool, or a direct API-based integration.

There are currently no exceptions by provider or ingestion path: if you are following the Custom Call Recorder setup, the App Type value is always custom_call_recorder.

Related documentation

For complete setup steps, required fields, and example payloads, refer to the Custom Call Recorder setup guide in the Pylon documentation. That article is the canonical reference for:

• Full field descriptions for Custom Call Recorder requests.

• Example configurations (including Zapier-based flows).

• Testing and troubleshooting Custom Call Recorder integrations.