Before you start
- You need an HTTPS endpoint that accepts
POSTrequests withContent-Type: application/json. For Power Automate, create a flow with the When a HTTP request is received trigger. - The URL must be
https://and point to a public host. MSPortal rejects localhost, private IP ranges (10.x, 192.168.x, 172.16-31.x), link-local, and carrier-grade NAT addresses. - The receiving workflow can act as soon as it gets a request, so use a test flow first.
Set up a webhook
Open the template
Expand Flow Webhook (JSON)
Turn on delivery
Choose a Delivery mode
- Create PSA ticket + webhook creates the ticket as usual and also sends the JSON.
- Webhook only sends the JSON and skips PSA ticket creation.
Paste the Webhook URL
Add a shared secret (optional)
X-MSPortal-Signature header your flow can verify. Leave it blank to skip signing. Do not put secrets in the URL.Send a test event
ticket.test request using your template’s field keys with sample values. The company and contact IDs in a test are samples too (TEST-COMPANY, TEST-CONTACT), so no real client is named. A message such as “Test sent (HTTP 200). Check your Flow run history.” confirms delivery. The test does not save the template, and your receiving flow can still take real actions.Save the template
Send submissions to Rewst
If your tenant has saved a Rewst connection in Settings > Integrations, Flow Webhook (JSON) shows a Send submissions to choice. Choose Rewst, then pick a saved connection under Rewst connection. Without a saved connection, the choice does not appear. The trigger URL and secret key stay on the connection, so you do not paste a URL or shared secret on the template. Rewst receives the key in thex-rewst-secret header. Manage Rewst connections opens integration settings; testing or saving a connection needs permission to manage integrations.
If the selected connection is removed, the template shows The selected Rewst connection no longer exists. Click Custom webhook URL and enter an endpoint, or pick another connection. Choose Custom webhook URL at any time to use your own endpoint with the shared secret described above.
Test with a request inspector first
A free request inspector such as webhook.site shows exactly what MSPortal sends before you build any flow logic.Get a unique URL
Paste it into MSPortal
Send a test event
Inspect the payload
Connect Power Automate
Create the flow
Save once to generate the URL
Copy the HTTP POST URL
Paste it into MSPortal and test
Generate the schema
fields.username, company.external_id, and the other properties as dynamic content.A schema generated from one sample accepts only that sample’s types, and some properties change type between requests. Before you rely on the schema, edit it so these allow both:company.id,company.external_idandcontact.external_id: text ornull.contact.impersonated_by:null, or an object withnameandemail.- Every key under
fieldsthat is optional on the form: its type ornull.
"type": ["string", "null"], or remove the type line for that property. Otherwise Parse JSON fails on the first request that sends the other type.Build the rest of the flow
Make a webhook-only template
Use this for requests that live entirely outside the PSA.Set the delivery mode
Clear old PSA defaults (optional)
Enter the URL and save
Branches
A branch with no webhook of its own sends its requests to the main form’s webhook. Set the webhook once on the main form and every client on a branch is covered, including branches you add later. Open a branch and expand Flow Webhook (JSON) to see which applies:- This branch uses the main form’s webhook names the delivery mode and where requests go. A change to the main form’s webhook applies to the branch too.
- Check Use a different webhook for this branch to give the branch its own settings. From then on only the branch’s webhook runs for requests made on that branch. The main form’s does not, even if you leave the branch’s webhook switched off.
- Clear Use a different webhook for this branch and save to go back to the main form’s webhook.
What happens on each submission
Retries
MSPortal sends each request once while the person submits. If that attempt fails in a way another attempt can fix, MSPortal tries again on its own:- Retried: no response within 10 seconds, a connection error, and HTTP 408, 425, 429 or any 5xx.
- Not retried: any other 4xx. The receiver refused the request as sent, and the same body would be refused again.
- Same request every time: each attempt sends the identical body, with the same
request_idandX-MSPortal-Request-Id, and the same signature.X-MSPortal-Delivery-Attemptcounts the attempts. If your workflow processed an attempt that MSPortal timed out on, the repeat carries arequest_idyou have already seen, so store that ID and skip a request you have handled. - Current settings: a retry goes to the form’s webhook as it is saved at that moment. Fix a wrong URL and save, and the waiting requests reach the corrected URL. Turn the webhook off and a waiting request is treated as failed at its next attempt.
- When every attempt fails: a request whose only destination was the webhook (Webhook only, or no PSA connected) is emailed to your fallback inbox, the same inbox used when PSA ticket creation fails. A request that also created a PSA ticket is not emailed, because the ticket holds it.
The JSON payload
Top-level shape
Top-level shape
"event": "ticket.submitted" and your tenant ID. Test events use "event": "ticket.test" and the literal tenant ID "test-tenant".request_id is unique to one submission and identical on every retry of it. Use it to match a request to the Submissions list and to skip one you have already handled.Who the request is for: company
Who the request is for: company
company.external_id is filled whenever the client company is linked to a company in the PSA you selected for tickets. It is the same on a main form and on its branches, in both delivery modes, and for requests made by client contacts and by your staff on a client’s behalf. It is null when:- the client company is not linked to a PSA company (check Settings > Integrations, your PSA, company mapping);
- no PSA is connected; or
- one of your staff submitted the form without choosing a company.
Who sent the request: contact
Who sent the request: contact
fields.When one of your staff uses View as to act as a client user, contact names that client user and contact.impersonated_by names the staff member. A workflow that acts on the requester’s authority should check that contact.impersonated_by is null.The fields object
The fields object
fields uses your template’s own field keys. A template with fields username, asset_tag, and reason sends:null. Multi-select answers arrive as arrays, numbers as numbers, and checkboxes as booleans.The ticket object
The ticket object
ticket.summary and ticket.description carry the request’s subject and description. ticket.id, ticket.number, ticket.external_url, ticket.board, ticket.status, and ticket.priority are always null: the webhook sends the submission, not the PSA ticket made from it. To find the PSA ticket for a request, look the request up in Submissions, where the export lists its ticket number.Headers
Headers
Verify the signature
When a shared secret is set, computeHMAC-SHA256(secret, raw request body) as lowercase hex, add the sha256= prefix, and compare it to X-MSPortal-Signature. Use the raw body bytes before you parse or re-serialize the JSON.
A valid signature shows the sender knew the secret. It does not stop a request from being replayed, so make your receiver safe to run twice for any step that must not repeat.
List and export submissions
Open the saved template and expand Flow Webhook (JSON). Submissions lists every request the form sent to the webhook, newest first. A main form includes the requests made on its branches, each marked with its branch name. A branch lists its own. The list and the export follow the company selector: with a company selected, they show that company’s requests only. The list updates on its own while it is open. A form with no webhook still shows Submissions when it has requests to list: those sent before its webhook was turned off, or by a branch that has a webhook of its own. Each request shows:- its status: Delivered, Retrying with the time of the next attempt, or Not delivered;
- when it was submitted, the number of attempts when there was more than one, and the last HTTP status;
- the client company with its PSA company ID, and the requester’s email;
- the inbox it was emailed to, if delivery failed and MSPortal used the fallback;
- the receiver’s error, when there was one; and
- its request ID, the
request_idyour workflow received.
request_id, submitted_at, form, branch, company_name, company_external_id, contact_name, contact_email, contact_external_id, contact_user_type, summary, ticket_number, delivery_mode, status, attempts, last_http_status, last_error, last_attempt_at, delivered_at, next_attempt_at, fallback_email_to
Times are in UTC. status is delivered, retrying or failed. One file holds up to 10,000 requests, the newest first; choose a shorter range if a form has more.
Requests sent before this list existed are included, without a PSA company ID or contact ID. Test events are not requests, so they are not listed here: Settings > Audit > Ticketing records them, along with every individual attempt. MSPortal sees only the HTTP result, so also check your receiving flow’s run history.
See every form’s requests in one place
Settings > Audit > Workflows lists the requests of all your forms together, newest first. Each row shows when the request was submitted, its status, the form and branch, the client company with its PSA company ID, who submitted it, the number of attempts, and the result: the last HTTP status, the receiver’s error, the time of the next attempt, or the inbox the request was emailed to. Turn on the Request ID column to match a row to therequest_id your workflow received.
Choose Today, Last 7 days or Last 30 days, filter by status, and search by form, branch, company, requester, summary or request ID. The list follows the company selector.
The tab has its own permission, Audit: Workflows, so you can give a reviewer this tab and nothing else in Settings. Every role that had Audit: Ticketing when the tab arrived received the new permission.
Embedded templates
If a template contains an embedded template, each template’s own webhook fires on its own. The parent’s webhook fires for the parent submission, and each embedded template’s webhook fires for that embed’s ticket. Test the nesting you plan to use. To stop an embed from firing a webhook, leave it unconfigured on the embedded template.Troubleshooting
Frequently asked questions
Does Send test event save my settings?
Does Send test event save my settings?
Can the test event trigger real actions?
Can the test event trigger real actions?
ticket.test and handle it safely. Use a controlled test path.How do I stop a template from creating PSA tickets?
How do I stop a template from creating PSA tickets?
Does HTTP 200 prove my provisioning flow finished?
Does HTTP 200 prove my provisioning flow finished?
Should I resubmit after a timeout?
Should I resubmit after a timeout?
request_id. Check Submissions, your flow, and the PSA first. A timeout does not prove nothing happened, and resubmitting creates a second request with a new request_id.Do branches use the main form's webhook?
Do branches use the main form's webhook?
Can I point several forms at one endpoint?
Can I point several forms at one endpoint?
template.key to tell the forms apart and company.external_id to tell the clients apart. Both arrive on every request.Can the person filling in the form change contact.email?
Can the person filling in the form change contact.email?