OP, the hard part about automating a strategy is not the actual decision-making process of when to enter a trade (unless it's some complex chart pattern). It's the infrastructure around that to manage the trade, handle any problems with contract overruns (i.e., out-of-sequence cancel requests and buy/sell orders due to speed of the market, typically solved by a state machine) and any disconnect/reconnect problems which may occur.
There are commercial solutions which can take you part of the way there, providing you the infrastructure I mentioned above, where you are left to focus on just the entry/exit logic. THE PROBLEM with these commercial solutions is that when analysis needs to shift a to tick-by-tick basis for decision-making rather than bar close decisions, their software logic (the part you never have to code) can eat up your CPU to the point that you cannot stay in-sync with the market.
Think of every tick coming into your PC as a real-time loop where you need to analyze it with what you already have for data and your software needs to fully analyze that before the next tick comes in. You know how in games they'll report "frame overruns" to you? Same kinda thing. Your software wasn't fast enough to analyze the real-time info so you got "blown out of a frame" where, in the trading case, it's new data coming in but your software is not ready for the new analysis because your last loop through real-time was too slow.
This is why you see guys on these forums hardly ever recommending something built on top of a charting package. They'll usually code in C++ with no unnecessary overhead between the autotrading software and the real-time data coming in. It's probably okay for strictly bar close decision-making but tends to break down if you want to also look at the tick level in intraday autotrading. Some vendors will try to compensate by doing something called "tick throttling" where the tick-by-tick logic is skipped and the ticks are looked at in like 200-500 "tick chunks" which could be considered as synthetic bar closes inside an actual bar close of like a 1-5 min timeframe.
Anyway, since you don't program, I'm going over your head on some things here but maybe I've opened your eyes a little to the realities of what you want to do.