Hi Mark, You can use GeneratFlowFile as the initial processor to trigger your flow.
Make sure to change the run schedule appropriately otherwise you will get a lot of flow files generated. -Bryan On Thu, Oct 19, 2017 at 10:08 PM Mark Rachelski <[email protected]> wrote: > I have a scenario where I need to make an HTTP request to an API but > taking context into account from previous invocations. Specifically, one > query string parameter is a time where the API returns all records from > that time or later. Every day, I would issue a new request using the > previous time requested. > > I have worked out that I can store the last time requested in the state > store. And use an UpdateAttributes process to retrieve it or initialize it > on the first run. I can then feed that into the InvokeHTTP processor and > build a dynamic URL from that attribute. > > But my main problem is that I don't know what beginning processor to use > in this flow. UpdateAttribute needs an inbound connection. And there are no > obvious 'dummy' beginning processors that I can find in the vast array. The > only thing I need from the beginning processor is the schedule tab. > > Any ideas on what my first processor in this flow should be? > > Thank you in advance for any help, > Mark. > -- Sent from Gmail Mobile
