n8n integration for repair shop automation

Create the n8n integration in BytePhase and copy the endpoint URL and API key. In n8n, end your workflow with a standard HTTP Request node posting JSON to that URL with the key in a header. Choose your default destination, activate, and submissions start flowing.

No, it’s optional. Install the BytePhase community node (n8n-nodes-bytephase, needs n8n 1.x) to create leads and self check-ins from a ready-made step, or use n8n’s built-in HTTP Request node, which works on self-hosted n8n and n8n Cloud alike.

You can connect it on every BytePhase plan, and the integration itself costs nothing extra. Each submission becomes a lead or a self check-in, and both of those are part of the Standard and Enterprise plans (and the 15-day free trial), so you need one of those to work with what comes in. Compare plans on the pricing page.

Documented plain-English names such as name, email, mobile_number, device_type, device_brand, device_model, serial_number and comment — a field reference inside BytePhase lists every field for each destination. Device names are matched to your catalogue, and unknown brands or models are kept as custom names.

A lead — an enquiry with contact and device details ready to follow up — or a self check-in, a device intake that Reception converts into a full job in one click. Send the destination with each call or set a default in BytePhase.

Send an Idempotency-Key header and the retried call returns the original result instead of creating a second record. Separately, your duplicate policy decides whether a repeat customer is skipped or creates a new record, matched by email or mobile.

Yes. The API key is shown once and stored only as a SHA-256 hash, every request is authenticated, rate-limited and scoped to your shop alone, and you can rotate the key in one click — the old key stops working instantly.

Yes. The HTTP Request node with a Header Auth credential works on either. The BytePhase community node needs n8n 1.x, and on n8n Cloud community nodes must be enabled. Every call goes out from n8n to BytePhase, so a self-hosted n8n on a private network works as long as it can reach the internet. Nothing needs to be exposed.

BytePhase does not call n8n, because it does not send outbound webhooks. To react to new records, run a scheduled workflow that polls BytePhase’s read endpoints. Those need a separate key created with the Zapier type, since only that type can read customers, leads, repairs and payments. Keep that key out of anything public.

Up to 60 requests a minute per API key. The limit is keyed on your key, not on n8n Cloud’s shared IP addresses, so other n8n customers cannot throttle you. A scheduled workflow should call BytePhase no more than once a minute per key, and a loop over many items should add a short Wait between items.

Point an HTTP Request node at your workspace’s integrations ping address with your Header Auth credential and execute it. A connected status means you are set; a 401 means the key or header is wrong, and a 412 means the workspace address is wrong. Then execute your create node once and the submission appears on the integration’s Activity screen.

Rotating the key on the integration’s Activity screen stops the old key immediately, with no overlap period. Copy the new key, which is shown once, and update the Header Auth credential in n8n. Every workflow using that credential picks up the new key. Until you update it, those calls are rejected as unauthorised.