When can the webhook be bound to a tenant?

get-help
22

I just test .

kumo.on('should_enqueue_log_record', function(msg, hook_name)
  local log_record = msg:get_meta 'log_record'
  print('should_enqueue_log_record>queue>log_record.queue -->',log_record.queue)
  local campaign = msg:get_meta('campaign')
  local queue = msg:get_meta('queue')
  local queue = msg:get_meta('mygoon')
  local received_from = msg:get_meta('received_from')
  print('should_enqueue_log_record: campaign,queue,mygoon,received_from -->',campaign,queue,mygoon,received_from)

  if log_record.queue ~= 'kafka' then
--     msg:set_meta('queue', 'kafka')
    return true
  end
  return false
end)

for this code campaign,queue,mygoon,received_from are all nil . it will be only get some infomation from log_reccord .
from the doc :https://docs.kumomta.com/reference/events/should_enqueue_log_record/?h=log_record said :

When enabled, each log record will generate a new Message object with the following attributes:

Sender will be set to the sender of the originating message
Recipient will be set to the recipient of the originating message
the log_record meta value will be set to the Log Record that is being logged
The message body/data will be set to the textual representation of the log record. By default this will be the JSON serialization of the log record, but if you have enabled templating using the per_record parameter to kumo.configure_log_hook then it will be whatever your template evaluated to for that record.
The reception_protocol meta value will be set to “LogRecord”

23

btw.
print(‘should_enqueue_log_record>queue>log_record.queue -->’,log_record.queue) is right .
print(‘should_enqueue_log_record: campaign,queue,mygoon,received_from -->’,campaign,queue,mygoon,received_from) all are nil .

24

https://imgur.la/images/2025/03/07/D241F86F-C09D-4AB7-BBD1-87F4A81A6425.png

25

Right sorry, I forgot we were talking about loghooks and actual messages.
First step is to include the metadata in the log, then you can extract the tenant or campaign from the loghook for decision making. Basically the same thing I said above but pull the data from logs instead of messages

26

Thank you, Tom. Does that mean this value will appear in the headers of the actual messages or somewhere else (in the recipient’s email eml)?

27

No. meta data is never trasmitted with the message to an end user,

28

OK . Thank you . I will try how to incloude the metaedata in the log.

29

Please do not @ us, if you want expedited help you’re free to become a sponsor.

30

Sorry for that. I will try to use a different credit card. In my country, there are relatively more restrictions on credit cards. Sorry again.

31

I meant in terms of a contract, not a Discord subscriber. Discord subscribers are appreciated, but the monthly fee there does not buy a support engagement. That said, none of this is to say that you cannot continue to ask questions and get help, just that @ messaging us is reserved for sponsors (who get their own private channel on the server).

32

OK got it .