Zapier
Jawwws Bytes is publicly available in the Zapier App Directory:
https://zapier.com/apps/jawwws-bytes/integrations
The Zapier adapter uses the maintained Bytes Developer API rather than browser or Admin routes. Each connection authenticates with a workspace Developer API key and remains subject to normal workspace isolation, plan entitlements, validation, Link limits, rate limits and safety controls.
Current operations
The first public integration supports:
- New Link polling trigger
- Create Link action
- Find Link search
- Add Tag to Link action
Zap editor helpers can also list Activity Groups, Links and Tags where the workflow needs an existing Bytes object.
Authentication
Zapier connects to one Bytes workspace using a Developer API key.
Create the key in:
Workspace Settings -> Developer API
Store the key only in Zapier's Bytes connection. Do not expose it as a Zap field, output, log value or public configuration value.
See Authentication for the Developer API credential rules.
API boundary
The Zapier integration is an adapter over supported /api/v1/* operations. Marketplace publication does not create a second API surface or make undocumented Bytes capabilities available.
The current public Zapier release does not include:
- Link click triggers
- Analytics events
- QR activity triggers
- Offline Engagement activity triggers
- browser/session webhook endpoint management
The New Link trigger uses polling because public Developer API webhook subscription management is not part of the current supported contract.
Plan behaviour
Developer API access is included on every Bytes plan. Zapier therefore does not add a separate API-access paywall.
The underlying Bytes action still enforces the workspace's normal entitlement and limits. For example, creating a Link through Zapier must pass the same active-Link allowance and validation as creating it in Bytes.