The fields your office receives
| Source field | Destination |
|---|---|
| Event type and call outcome | Zap trigger and filter conditions |
| Caller and captured intake details | Fields you map into the destination app |
| Call summary | Your chosen note, description, or message field |
| Call reference and event time | Source 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
Connect Penny inside Zapier
Create a Zap and select Penny. Connect it with the API key from Settings → Integrations, using the invite link shown there.
- 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. Press Test in Settings → Integrations to send a sample, then make one test call.
- 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
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 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
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.