Skip to content
Penny
Log inTry Penny free

Automation · Via Zapier or your workflow · Starter

A finished Penny call starts the next job in your Zap.

Put the lead in a sheet, create a callback task, or file an inquiry in the app your office uses. Penny supplies the call details; your Zap decides which calls qualify and where those details go.

Try Penny freeRead the setup guide

14 days of Pro included. No credit card.

The fields your office receives

Source fieldDestination
Event type and call outcomeZap trigger and filter conditions
Caller and captured intake detailsFields you map into the destination app
Call summaryYour chosen note, description, or message field
Call reference and event timeSource reference and date fields
Direction
Penny supplies the event to Zapier. Your Zap runs its selected actions in the connected destination apps.
When it happens
Triggers run after call processing. The selected event determines which calls start the workflow; task timing also depends on Zapier and the destination app.

These triggers move captured call data. A Zap cannot instruct Penny to place a call or make an appointment. A booking event should be interpreted with its destination: field-service intake still needs office scheduling.

Set up the connection

  1. 1

    Connect Penny inside Zapier

    Create a Zap and select Penny. Use the connection credential or authorization flow provided in Penny’s Integrations settings for your account.

  2. 2

    Choose a trigger with a purpose

    Use the lead trigger for new inquiries, a message trigger for callbacks, or a completed-call trigger when every processed call belongs in the workflow. Load a marked test call.

  3. 3

    Map the destination fields

    Connect the destination app and map the captured details. Use the stable call reference to recognize the source call. Set a fallback when a field the destination requires was not supplied.

  4. 4

    Test, enable, and review failures

    Run the test action and inspect the record in the destination app. Enable the Zap once the mapping is right, then use Zapier task history to investigate failed actions.

Penny’s signed call-completed webhook settings
The signed webhook is an alternative input to your Zapier workflow. Sample endpoint; no account connection or signing secret is shown. Your receiving workflow determines the destination object.

Illustrative Penny event mapped in Zapier

Event
Lead captured
Summary
Caller requests an estimate for a new fence
Captured service address
100 Example Lane
Destination action
Create an inquiry record in the app you chose
Sample event: a captured inquiry becomes the record your office’s Zap is set to create.

Check the first result

Compare the source test event with the resulting record. Confirm the workflow ignores irrelevant calls and that missing fields do not become blank overwrites or invented values.

Questions about this connection

Which calls should start my Zap?

Choose the trigger for the work you want: a lead for new inquiries, a message for callbacks, or a completed call for your call log. Add filters and test a call that should be excluded as well as one that should pass.

How do I know the connection is ready?

Compare the source test event with the resulting record. Confirm the workflow ignores irrelevant calls and that missing fields do not become blank overwrites or invented values.

Browse all connections