jdZddlZddlZddlmZddlmZejeZ dZ de fdZ dde d e d e d e d e d e de fdZy)aA tenant's connected Mailchimp account, and sending through it. The connection is written by the dashboard's Mailchimp connect flow into the tenant's own schema -- the same galaxiq_tenants database and per-tenant `integrations` table that strategist_settings lives beside (see app/services/infra/database.py's get_setting). This is deliberately NOT app/services/integrations/platform.py: that module reads/writes a differently-shaped `integrations` table in the separate galaxiq_master database, used today only for this backend's own Shopify OAuth writes. A tenant connecting Mailchimp, Facebook, Pinterest, etc. through the dashboard never touches that table -- it lands here instead. N)sql)get_db_connectionz2https://mandrillapp.com/api/1.0/messages/send.json tenant_idc  t} |j 5}|j t jdjt j||j}ddd|jr|ddk7ry|dxsi}|jdxsijd }|sy||jd xsd |jd xsd d S#t$r%}tjd|d|Yd}~yd}~wwxYw#1swYxYw#t$r5}tjd|d|Yd}~|jyd}~wwxYw#|jwxYw)aZThis tenant's active Mailchimp connection, or None. Returns {"transactional_api_key", "from_email", "from_name"} -- everything send_via_mandrill needs. None covers every reason it cannot be used: no connection, a disconnected/revoked one, or a connection made before SMS Mode existed that never captured a transactional key. z,Could not read the Mailchimp connection for : NzISELECT metadata, status FROM {}.integrations WHERE provider = 'mailchimp'ACTIVErsmstransactionalApiKeyemail accountName)transactional_api_key from_email from_name) r ExceptionloggererrorcursorexecuterSQLformat Identifierfetchonecloseget)rconnexcurrowmetadataapi_keys B/var/www/html/strategist-ai/app/services/integrations/mailchimp.pyget_mailchimp_connectionr$sj "  [[] !c KK78y12 4,,.C  ! #a&H$1v|H||E"(b--.CDG ") ll7+1r\\-06B 9  CI;bQSPTUV  ! !  CI;bQSPTUV  sX C3D0AD$4D03 D!<DD!$D-)D00 E.9E)E1)E..E11F connection to_addresssubjecttexthtmlreply_toreturncF|d|dxsd|ddg|||d}|rd|i|d<|d |d } tjt|d }|j|j } | r| dni} | jddvrH| jdxs| jdxsd} t jd|d| dddSt jd|d|d||dS#t $r,} t jd |d| ddddcYd} ~ Sd} ~ wwxYw)aSend one email through Mailchimp Transactional (Mandrill). Never raises for a delivery failure -- mirrors send_email's own contract, since this is one of its branches. Error details are deliberately generic (no vendor name, no Mandrill reject reason): the chat model relays a tool error's detail straight into what it tells the customer, and neither is something a customer waiting on an email should see. rrNto)r type)rrr-r'r(r)zReply-Toheadersr)keymessage)jsontimeoutzMandrill send to z failed: T)exc_inforzCould not send the email.)statusdetailrr6)sentqueued scheduled reject_reasonrejectedzMandrill rejected email to rzMAILCHIMP EMAIL SENT | to=z | subject=r8)r6r-r') httpxpostMANDRILL_SEND_URLraise_for_statusr3rrrrinfo) r%r&r'r(r)r*r1payloadresponseresultsroutcomereasons r#send_via_mandrillrGJsU!. ,4#T23 G((3  !89gNGJ::/grJ!!#--/$gajG{{8$CC_-TX1FT* 2:,bIJ!-HII KK,ZL G;OPJ7 CC J ( IbTBT R!-HIIJsrRs  9   8 $H..d=A'D$'DC'D#'D'D'*'D69'DEI'DrQ