# Send Actions to NiFi

To check that your NiFi Ingest dataflow is ready to receive actions, you can send a `GetStatus` action. For example, if you configured your "Connector ACI" group to listen on port 10000, you might send the following HTTP request:

    http://host:10000/action=getstatus

You can send this request from a web browser, or use a tool such as cURL. The server returns the following response:

    <autnresponse>
        <action>GETSTATUS</action>
        <response>SUCCESS</response>
        <responsedata>
            <product>idol.nifi.processor.HandleAciRequest</product>
            <version>12.10.0</version>
            <aciport>10000</aciport>
        </responsedata>
    </autnresponse>

## Synchronous and Asynchronous Actions

Some actions are synchronous and others are asynchronous:

- NiFi Ingest does not respond to a synchronous action until it has completed the request. The result of the action is included in the response. `GetStatus` is an example of a synchronous action.
- NiFi Ingest responds to an asynchronous action immediately. The request is added to a queue and the response contains only a token. You can use this token to determine the status of the request, and obtain the results of the action. Actions that take a long time to complete are often implemented as asynchronous actions, so that you get an immediate response and can check back later to see whether the task has finished. `Synchronize` is an example of an asynchronous action - depending on the size of the data repository and the configuration of the connector, it could take hours to synchronize all of the data.

To check the status of an asynchronous action, use the QueueInfo action.

_FT_HTML5_bannerTitle.htm