Skip to main content

FAQ

Does it work on custom objects?​

Yes. When you create a webhook, the Target Object can be a standard object such as Lead or Account, or any custom object — for example Student__c or CISC__Lead__c. See Create a Webhook.

Does it work with Flows?​

Yes. Webhook Studio provides a Send Webhook invocable action (SendWebhook) that you can add to a Record-Triggered Flow, a Scheduled Flow, or a Screen Flow. See Use with Flows.

Do I need code?​

No. You install the app, set up a Named Credential, and create webhooks by filling in a form. No code is needed.

Where are secrets stored?​

Secrets are stored in the Named Credential, which Salesforce protects. They are never stored in the webhook configuration (bytenex__Webhook_Config__c) — the configuration only refers to the Named Credential by its Developer Name. See Setup: Named Credential.

What are the limits?​

Failed deliveries are retried with exponential backoff, up to 3 retries, and you can also retry manually from a log entry. For any other limit that matters to your use case, contact Support and ask before you build around it — this page does not guess at numbers.

Is it free?​

Yes — ByteNex Webhook Studio is a free app, as described on the homepage.

How do I report a bug?​

Email contact@bytenex.io with what you did, what you expected, and what happened. A log entry from the Logs tab — its status and status code — helps us find the problem faster. See Support.

Does it support both outbound and inbound webhooks?​

Yes. Outbound webhooks send record changes from Salesforce to any endpoint, and inbound webhooks receive data into Salesforce and create or update a Lead. See Overview and Inbound Webhooks.


Was this helpful? Let us know by email — we read every message.