Webhooks can be used to run a workspace without using engine time.

Webhooks can be used to run a workspace without using engine time.

• A. True
• B. False
• C. Only when authenticated
• D. It depends on the app

Answer: (A)

Webhooks enable event-driven triggering of a workspace on FME Server. You can have an external system call a webhook endpoint to start a workspace run without needing to start it from the UI or with a continuous polling setup. The action of hitting the webhook itself doesn’t consume engine time on your side; the actual processing time is spent by the FME Engine on the server during the workspace run. So you can initiate a run without using engine time in your own environment—the engine time is incurred on the server as part of the workspace execution. This isn’t about authentication or app dependency; those factors don’t change the fact that the webhook serves as a remote trigger that starts processing on the server.

Webhooks enable event-driven triggering of a workspace on FME Server. You can have an external system call a webhook endpoint to start a workspace run without needing to start it from the UI or with a continuous polling setup. The action of hitting the webhook itself doesn’t consume engine time on your side; the actual processing time is spent by the FME Engine on the server during the workspace run. So you can initiate a run without using engine time in your own environment—the engine time is incurred on the server as part of the workspace execution. This isn’t about authentication or app dependency; those factors don’t change the fact that the webhook serves as a remote trigger that starts processing on the server.