Skip to main content
A ticket template can send a JSON copy of every submission to a webhook URL you control. Use it to start a Power Automate, Logic Apps, n8n, or Zapier workflow, or as the only destination for requests that should never create a PSA ticket, such as HR change requests or approvals. This guide is for MSP staff whose role can write or manage ticket settings.

Before you start

  • You need an HTTPS endpoint that accepts POST requests with Content-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

1

Open the template

Go to Settings > Tickets > Templates and open the template.
2

Expand Flow Webhook (JSON)

Scroll past PSA Integration Settings and click Flow Webhook (JSON) to expand it.
3

Turn on delivery

Check Send submissions to a Flow webhook.
4

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.
Choosing Webhook only also clears any TimeZest appointment scheduling on the template, because no ticket exists to schedule against.
5

Paste the Webhook URL

Paste your endpoint into Webhook URL (https only). In Power Automate, copy it from the When a HTTP request is received trigger.
6

Add a shared secret (optional)

Enter a random string in Shared secret (optional). Every request then carries an X-MSPortal-Signature header your flow can verify. Leave it blank to skip signing. Do not put secrets in the URL.
7

Send a test event

Click Send test event. MSPortal posts a 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.
8

Save the template

Click Save Template. Real submissions use the saved configuration, not the unsaved editor values.

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 the x-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.
1

Get a unique URL

Open webhook.site. It creates a unique URL for you. Copy it.
2

Paste it into MSPortal

In Flow Webhook (JSON), paste the URL into Webhook URL (https only) and check Send submissions to a Flow webhook.
3

Send a test event

Click Send test event. The request appears in the inspector within a couple of seconds.
4

Inspect the payload

Click the request to see the headers and JSON body. This is the shape your flow receives. Copy the body for the next section.
Save the template and submit a real request with the inspector URL still in place to see a production payload, including the client’s PSA company ID. Then swap in your real flow URL. Do not send sensitive production data to a public inspection service.

Connect Power Automate

1

Create the flow

In Power Automate, create an instant or automated cloud flow and choose the When a HTTP request is received trigger.
2

Save once to generate the URL

Power Automate only issues the URL after the flow is saved with the trigger in place. Add a placeholder action, such as a Compose with a static value, and click Save.
3

Copy the HTTP POST URL

Reopen the trigger and copy HTTP POST URL.
4

Paste it into MSPortal and test

Paste the URL into Webhook URL (https only), check Send submissions to a Flow webhook, and click Send test event.
5

Generate the schema

In the trigger, click Use sample payload to generate schema and paste the JSON body you captured. Power Automate then offers 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_id and contact.external_id: text or null.
  • contact.impersonated_by: null, or an object with name and email.
  • Every key under fields that is optional on the form: its type or null.
In Power Automate, write a nullable property as "type": ["string", "null"], or remove the type line for that property. Otherwise Parse JSON fails on the first request that sends the other type.
6

Build the rest of the flow

Add the actions you want, such as a SharePoint list item, a Teams message, or a database write.
The Power Automate trigger URL is itself a secret. If the flow provisions, deletes, or changes credentials, set a shared secret in MSPortal and verify X-MSPortal-Signature in the first step of the flow.

Make a webhook-only template

Use this for requests that live entirely outside the PSA.
1

Set the delivery mode

In Flow Webhook (JSON), check Send submissions to a Flow webhook and choose Webhook only. The PSA Integration Settings section is then disabled for the template.
2

Clear old PSA defaults (optional)

If the template still holds a board, priority, or status, open PSA Integration Settings and click Clear PSA defaults so no stale routing remains.
3

Enter the URL and save

Add the Webhook URL (https only), then click Save Template. The Flow Webhook (JSON) header shows a Webhook only badge.
Webhook-only templates still follow company visibility, role access, and required-field rules. The requester sees Request submitted when the workflow accepts the request, and also when it did not answer and MSPortal has queued the request to try again. If the workflow refuses the request, or every attempt fails, MSPortal emails the request to your fallback inbox so it is not lost. See Retries.

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

Each attempt waits up to 10 seconds for a response.

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_id and X-MSPortal-Request-Id, and the same signature. X-MSPortal-Delivery-Attempt counts the attempts. If your workflow processed an attempt that MSPortal timed out on, the repeat carries a request_id you 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 requester is not asked to do anything while MSPortal retries. Do not submit the same real request again after a timeout: check Submissions first.

The JSON payload

Real submissions use "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.
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.
A client linked to several PSA companies sends the one the requester’s own PSA contact belongs to.
The contact is never a form answer. MSPortal reads it from the session of the person who submitted, whether they signed in with Microsoft, Google or an email link, so someone filling in the form cannot change it. Email addresses a form asks for, such as a new hire’s address, arrive in 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.
fields uses your template’s own field keys. A template with fields username, asset_tag, and reason sends:
Every field key in the template is present. Unanswered optional fields are null. Multi-select answers arrive as arrays, numbers as numbers, and checkboxes as booleans.
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.

Verify the signature

When a shared secret is set, compute HMAC-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_id your workflow received.
To reconcile against what your workflow received, choose an Export range (Last 7 days to Last 12 months) and click Export CSV. The file has one row per request, with these columns in every language: 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 the request_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

No. It sends a real request using the current editor values. Click Save Template before you expect real submissions to use them.
Yes. Your flow must recognize ticket.test and handle it safely. Use a controlled test path.
Choose Webhook only and save. Clearing individual PSA fields is not enough on its own.
No. It proves the endpoint accepted the request. Check the later steps and the final record in the receiving system.
No. MSPortal retries on its own, with the same 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.
Yes. A branch without its own webhook settings uses the main form’s, and keeps following it when it changes. A branch with Use a different webhook for this branch checked uses only its own. See Branches.
Yes. Use template.key to tell the forms apart and company.external_id to tell the clients apart. Both arrive on every request.
No. It is the signed-in person’s account email, read from their session. See Who sent the request: contact under The JSON payload.