# Example Action

The following is an example request that begins a synchronize task:

    host:10000/action=synchronize&ConnectorGroup=FileSystem

The value of the `ConnectorGroup` parameter must match the name you assigned to the connector group when you created the dataflow. The synchronize action is asynchronous so it returns only a token. You can use the token with the `QueueInfo` action to check the status of the task. For example:

    host:10000/action=queueinfo&queueaction=getstatus&queuename=synchronize&token=...

The following is an example response to the `QueueInfo` action which shows that the task has finished:

    <autnresponse>
        <action>QUEUEINFO</action>
        <response>SUCCESS</response>
        <responsedata>
            <actions>
                <action>
                    <status>Finished</status>
                    <queued_time>2019-Sep-05 15:44:43</queued_time>
                    <time_in_queue>0</time_in_queue>
                    <process_start_time>2019-Sep-05 15:44:43</process_start_time>
                    <time_processing>631</time_processing>
                    <process_end_time>2019-Sep-05 15:55:14</process_end_time>
                    <token>...</token>
                </action>
            </actions>
        </responsedata>
    </autnresponse>

After the task has finished, open the NiFi user interface in your web browser. You should see that the "Synchronize Output" queue from the "File System Connector" group contains a number of FlowFiles. These represent the changes to the file system since the last synchronize (for example, new documents, modified documents, and deleted documents). These FlowFiles can be routed into an ingestion pipeline, such as the one described in Build a Basic Ingestion Pipeline. The ingestion pipeline might perform various processing steps and then index the data into an IDOL Content component.

The "File System Connector" group also has "Collect Output", "Identifiers Output", and "Failure" outputs. Some actions, for example "delete" do not create FlowFiles (other than the response that is returned to the ConnectorGroupRouter and then to the Connector ACI group).

For more information about that actions that you can send to NiFi Ingest connector groups, see Connector Actions.

_FT_HTML5_bannerTitle.htm