You do not need to follow a fixed prompt format when using FIA. Write the strategy in plain English, but make the trading rules specific enough for FIA to understand what the automation should monitor, check, and do.
If information required for the automation is missing, FIA can ask a follow-up question.
Include the details that define your strategy, where applicable:
| Detail | What to describe | Example |
|---|---|---|
| Instrument or universe | What the strategy should monitor or trade | NIFTY, a specific stock, options, a watchlist |
| Timing | When the strategy should begin or be active | 9:20 AM, every trading day |
| Trigger | What starts the relevant workflow | Time, breakout, market event |
| Conditions | What must be true before proceeding | Price or indicator conditions |
| Action | What should happen when the rules are met | Place an order, send an alert |
| Quantity or order details | Required trading parameters | Quantity, lot size, product details |
| Risk rules | Conditions that control risk | Stop loss or portfolio limit |
| Exit rules | When the position or automation should stop | Target, stop loss, time-based exit |
| Frequency | How often a rule should be checked | Every five minutes |
You do not need to include fields that are irrelevant to your strategy.
The way you describe a value can change the automation logic.
For example:
“Alert when the live LTP is 10% above the price captured when the automation starts.”
This is different from:
“Alert when the intraday percentage change is above 10%.”
The first requires the starting price to be captured and retained. The second refers to a different calculation.
Expressions distinguish between strict and inclusive comparisons.
> 10.>= 10.< 10.<= 10.If that distinction matters to your strategy, state it clearly.
Start with the trading logic.
For example, it is usually clearer to say what value should be captured and what it should later be compared against than to choose a node without considering whether the value needs to stay fixed or remain live.
You can still specify a particular Automate node when you deliberately want that implementation.
| Scenario | What to do |
|---|---|
| What if all conditions must be true? | Say that every condition must be satisfied. The workflow can use the appropriate AND logic. |
| What if any one condition can trigger the next step? | State that the workflow should proceed when any of the specified conditions is met. |
| What if a value must be remembered from a specific time? | State when it should be captured and that it must remain fixed. This may require Declare Variable. |
| What if the calculation must keep updating? | State how often it should be checked or that it should use current data. This may require Expression Builder. |
Last updated: 26 Aug 2026