Question 1

What if a delivery fails?

Accepted Answer

It is logged as failed with the error, and you can retry it in one click from the activity screen. If deliveries keep failing, BytePhase shows a warning on the integration and emails you. Re-deliveries of the same response never create duplicates.

Question 2

Why do my fields look clean instead of q3_something?

Accepted Answer

BytePhase strips Jotform's internal question prefixes before showing you the detected fields, so you map fullName or deviceBrand — the names you actually gave your questions.

Question 3

What does a submission become in BytePhase?

Accepted Answer

Your choice per form: 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.

Question 4

How is the webhook secured?

Accepted Answer

The webhook URL embeds a key that 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 at any time — the old URL stops working the moment you do.

Question 5

Will resubmissions create duplicate records?

Accepted Answer

Only if you want them to. The duplicate policy matches by email or mobile and either skips the repeat or creates a new record. Jotform re-deliveries of the same submission are recognised by their submission ID and never create doubles.

Question 6

What if a delivery fails?

Accepted Answer

It is logged as failed with the error and can be retried in one click from the activity screen. If failures continue, BytePhase shows a warning on the integration and emails you before enquiries are lost.

Question 7

How do I connect n8n to BytePhase?

Accepted Answer

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.

Question 8

What fields can I send?

Accepted Answer

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.

Question 9

What does a call create in BytePhase?

Accepted Answer

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.

Question 10

What happens when a workflow retries?

Accepted Answer

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.

What if a delivery fails?

Why do my fields look clean instead of q3_something?

What does a submission become in BytePhase?

How is the webhook secured?

Will resubmissions create duplicate records?

What if a delivery fails?

How do I connect n8n to BytePhase?

What fields can I send?

What does a call create in BytePhase?

What happens when a workflow retries?

TRACKING COOKIES

THIRD PARTY EMBEDS

OUR PRIVACY POLICY

TERMS AND CONDITIONS