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.
In-product workflow discovery
Authenticated Bytes users can open Integrations -> Zapier -> Browse workflows to discover approved public Zapier workflows and start them through Zapier's embedded editor.
The Workflow Element is a discovery and editor surface over the same published Zapier integration. It does not create another Bytes API surface, expand the supported /api/v1/* operations or pass workspace API keys through the embed configuration.
When a workflow needs a Bytes connection, authentication continues through Zapier's normal connection experience. The canonical Open in Zapier route remains available as a fallback.
Zapier currently displays a Beta tag for Jawwws Bytes in the embedded editor. Do not interpret the in-product embed as evidence that Zapier has removed that provider lifecycle tag.
Current operations
The public integration supports:
- New Link polling trigger
- Create Link action
- Find Link search
- Add Tag to Link action
- Get Link QR action
Zap editor helpers can also list Activity Groups, Links and Tags where the workflow needs an existing Bytes object.
Get Link QR
Get Link QR retrieves the governed standard QR file for an existing Bytes Link through the public Developer API.
Supported formats are:
- PNG, the default;
- SVG;
- PDF.
PNG can also use an optional raster-size target. The Bytes QR renderer keeps whole QR modules, so the actual returned PNG width can be slightly smaller than the requested target. Zapier returns the QR as a file result and preserves the returned filename and MIME type for downstream file-aware steps.
This action does not expose Brand Kit styling, centre logos, arbitrary colours, output-profile selection or print-production controls.
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 scan/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.
Standard QR retrieval is available through the same governed Developer API contract. The underlying Bytes actions still enforce 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.