Zapier and Make automation brief

Zapier and Make are useful for lightweight operations, CRM handoff and campaign automation. Today they can call Perkamo HTTP endpoints or receive Perkamo webhooks. Native templates are planned around repeated customer scenarios.

Planned native scope

• Provide reusable actions for identifying customers and sending trusted events.
• Provide trigger templates for Perkamo webhook deliveries.
• Include idempotency guidance so repeated scenario runs do not duplicate points

or rewards.

• Add setup checks for server key scopes, endpoint reachability and recent errors.

These templates are not a replacement for a trusted production backend when checkout, billing or reward fulfillment is business-critical.

Available now

Use API requests and webhooks directly from the automation platform.

• Send events with POST /v1/events.
• Consume Perkamo effects with Webhooks.
• Use Concepts for transaction ids.
• Read Security and keys before storing server keys in an

automation platform.

Good first automations

• Add points after an approved offline action.
• Notify a team when a VIP perk unlocks.
• Sync a perk unlock to a CRM or helpdesk.
• Route failed fulfillment to an operator workflow.

Perkamo can help customers decide which automations are safe to run in Zapier or Make and which flows should stay in a backend service.