About asynchronous Rest API in application in flow designer

[Mamidi]

Hi All,

actually i am trying to get the trigger as Asynchronous Rest API in applications type so its not appearing there and i already installed jira spokes and i have the required roles in addition to that i have integration_hub_admin also so can you find out  what's wrong in this and where i am doing wrong 

[Matthew_13]

It looks like you’re on the right track, but a couple of things commonly trip people up here.

First, installing the Jira Spoke and having integration_hub_admin doesn’t control whether REST triggers appear. The Inbound / REST API trigger is a separate capability, so having the spoke and roles alone won’t make it show up.

Second, double-check what you’re creating. The REST/API trigger only appears when you’re building a Flow. If you’re in a Subflow or Action, you’ll only see things like Record, Scheduled, or Application triggers exactly what your screenshot shows.

Also, the trigger usually isn’t literally called “Asynchronous REST API.” In most versions, you select something like Inbound REST API or API Trigger, and then you configure it to respond asynchronously for example, returning a 202 instead of waiting for completion.

A couple quick things to try:

• Confirm you’re creating a Flow, not a Subflow or Action

• Make sure your scope is Global and reload Flow Designer

• Check Plugins to confirm the Inbound REST / API trigger capability is active

If you can confirm your ServiceNow version and whether this is a Flow or Subflow, it’ll be easy to point you to the exact trigger name and where the async option lives if you dont have.

@Mamidi - Please mark as Accepted Solution and Thumbs Up if you found Helpful!!

[Mamidi]

Hello @Matthew_13  actually i am doing it in flow and i had installed every necessary plugin for Rest api but its not showing in the application in flow ,that's what i am trying to solve so help me to resolve this .

[VaishnaviK43271]

Hi @Mamidi !!

Flow Designer does NOT have an “Asynchronous REST API” trigger, so it will never appear under Application triggers, even with Integration Hub and spokes installed.

REST calls cannot directly trigger a Flow. The supported pattern is:

REST API → Scripted REST API → Subflow

Correct approach:

1. Create a Scripted REST API (System Web Services → Scripted REST APIs).

2. In the REST resource script, call a Subflow using sn_fd.FlowAPI.startSubflow().

3. Design your logic in a Subflow (trigger = None).

startSubflow() runs asynchronously by default, so the REST call returns immediately while the subflow continues in the background.

The triggers you see (Inbound Email, Service Catalog, etc.) are event-based triggers only; REST is request-based and therefore not available as a Flow trigger.

Summary:

• No “Async REST API” trigger exists in Flow Designer

• Roles/plugins are not the issue

• Use Scripted REST API to invoke a Subflow

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for.

Thank You

[Mamidi]

Hi ,its coming for them for me its not coming the way it is that is my issue can you please explain how it can be done like this he also did the same process which i did so can you came with a solution to this.