Currently the rings will activate and then immediately activate again when sent a signal. I managed to get around this by pairing it with a clock so that the Go To signal is only passed for 10 ticks every 60, but it'd be nice if there was a slight delay so it wasn't necessary. (Especially given it's not the most reliable workaround - often it'll take several cycles to actually transport)

Currently the teleporter checks every 30th tick if signal is given.
If it is not occupied it will set itself occupied and schedule a teleport in next 0 to 300 ticks (due to how animations work).
Hopefully this can help with setting up circuits.

I will see how to adjust the logic for easier use.

Hello!
Alternatively, add another virtual signal - "goto-ring-id-time", and put the number of ticks in the settings.
For example, the user will be able to specify that items should be sent every ... seconds, that is, if you specify 18,000 ticks, the teleport will send items every 5 minutes (1 minute = 3,600 ticks, 1 second = 60 ticks), that is, it will simply work on a timer.
And the main signal will be used to instantly turn on the teleport when you need to send right now, or program your own scheme.

I cannot run teleporters with tick accuracy, all teleporters are tied to a global cycle, repeating every 5 seconds. This is due to how entity animations work. It would be possible to implement a timer though. Player could send virtual timer signal amount as seconds. Either it would be possible to:

Ignore teleport commands until "timer" seconds have passed from last teleport.
OR
If given "timer" value, teleporter will not trigger on goto signal, it will instead trigger every "timer" seconds to connect to location indicated with goto.

We would be very grateful if you could implement any logic that could trigger the teleport on a timer - it would make automation a bit easier :)
In principle, I can assemble a timer from combinators and attach a signal to it, but it would be amazing if you could implement this logic in code :)

Timer signals finally implemented in 0.3.0. See changelog for details.