I would like to setup my org-capture template for meetings so that I get automatically clocked into the meeting header on the day and time of the meeting. So given:
* Meeting with client
SCHEDULED: <2020-05-01 Fri 09:00-09:30>
I would like to be clocked into that issue on Friday morning at 9am.
If you just want to have these meetings reflected in your clock data afterwards for reporting purposes, I don't think you need to actually clock in and out? You can just add the clock data directly:
CLOCK: [2020-05-01 Fri 09:00]--[2020-05-01 Fri 09:30] => 0:30
You could come up with a capture template to let you enter the start/end times and put them in both the timestamp and the clock record. Another approach might be a function to scan an org file for meetings and add the clock info, i.e. something you run at the time you want to review the clock data.
org-capture. To be honest, I thought :clock-in t would do that, instead of what it does.
C-c .), which is what org recommends for meetings/appointments that occur at a specific time and then are over. Scheduling is more about when tasks should start showing up, and has different semantics if you don't complete the task when you planned to.