System Architecture
An engineering breakdown detailing the data lifecycle of an inbound lead submission on acuerdotech.com—from the client browser edge through serverless compute layers on Google Cloud Platform into enterprise database structures.
1. End-to-End Data Pipeline
The transaction architecture utilizes a completely decoupled, serverless event paradigm designed for absolute zero-maintenance availability, fast edge performance, and rigorous enterprise data isolation.
[ Frontend Layer ] [ Serverless Compute Layer ] [ Workspace / Storage Layer ]
Hostinger Edge GCP Cloud Run (Python 3.14) Google Workspace Ecosystem
────────────── ─────────────────────────── ───────────────────────────
User Form Submit ─────> HTTPS POST (CORS Guarded) ─────> Google Sheets API (Row Insert)
(Injected Secret Engine) ─────> Mailjet SMTP REST API (Alert)
2. Component Layer Deep-Dive
A. Static Client Edge (Hostinger)
The frontend interface is an optimized, static client-side asset deployed at edge. Crucially, the site context contains zero static API keys, tokens, or configuration secrets within its viewable source. When a discovery submission triggers, an asynchronous, non-blocking TLS 1.3 JavaScript fetch() dispatches the structured payload payloads directly to the compute layer.
B. Serverless Container Run (Google Cloud Platform)
The compute pipeline terminates at a fully managed Google Cloud Run service running a serverless Python 3.14 execution environment. The instance dynamically handles incoming data, resolves browser preflight CORS handshakes, auto-scales down to absolute zero when idle to eliminate cold infrastructure overhead, and handles request verification securely.
C. Cryptographic Injection (GCP Secret Manager)
To ensure institutional data protection, API authentication tokens and target Spreadsheet IDs are compiled and encrypted inside Google Cloud Secret Manager. The Cloud Run architecture utilizes native environment bindings to dynamically resolve values into volatile process memory at runtime, keeping the underlying deployment container completely sanitized and auditable.
D. Downstream Target Synchronization (Workspace & Mailjet)
Upon validating inputs, the compute agent exercises a dual API branch. First, it authenticates natively via IAM Application Default Credentials (ADC) to append entry matrices via the Google Sheets API. Concurrently, it builds an authenticated handshake over HTTPS to the Mailjet REST API engine, triggering atomic operational alerting to company coordinators.
3. Production Microservice Architecture
The implementation logic deployed inside our serverless instance features comprehensive sanitization and direct environment token mapping:
import functions_framework
import json
import os
import urllib.request
import base64
import google.auth
from googleapiclient.discovery import build
@functions_framework.http
def handle_lead(request):
# CORS policy enforcement for cross-origin tracking mitigation
if request.method == 'OPTIONS':
headers = {
'Access-Control-Allow-Origin': '*',
'Access-Control-Allow-Methods': 'POST',
'Access-Control-Allow-Headers': 'Content-Type',
'Access-Control-Max-Age': '3600'
}
return ('', 204, headers)
headers = {'Access-Control-Allow-Origin': '*'}
try:
# Secure dynamic extraction from local process environment mapping
spreadsheet_id = os.environ.get('SPREADSHEET_ID')
mailjet_api_key = os.environ.get('MAILJET_API_KEY')
mailjet_secret_key = os.environ.get('MAILJET_SECRET_KEY')
if not all([spreadsheet_id, mailjet_api_key, mailjet_secret_key]):
return (json.dumps({'error': 'Infrastructure configuration fault'}), 500, headers)
request_json = request.get_json(silent=True)
company = request_json.get('company')
bottleneck = request_json.get('bottleneck')
email = request_json.get('email')
timestamp = request_json.get('timestamp')
# Google Sheets Protocol Commit via Native IAM Account Identity
default_creds, project = google.auth.default(
scopes=['https://www.googleapis.com/auth/spreadsheets']
)
sheets_service = build('sheets', 'v4', credentials=default_creds, cache_discovery=False)
sheets_service.spreadsheets().values().append(
spreadsheetId=spreadsheet_id,
range='A:D',
valueInputOption='USER_ENTERED',
body={'values': [[timestamp, company, bottleneck, email]]}
).execute()
# Encrypted Multi-Channel Transactional Notification Routing
mailjet_url = "https://api.mailjet.com/v3.1/send"
email_data = {
"Messages": [{
"From": {"Email": "info@acuerdotech.com", "Name": "AcuerdoTech Engine"},
"To": [{"Email": "info@acuerdotech.com", "Name": "Operations"}],
"Subject": f"New Lead Inbound: {company}",
"TextPart": f"Company: {company}\nBottleneck: {bottleneck}\nEmail: {email}"
}]
}
auth_string = f"{mailjet_api_key}:{mailjet_secret_key}"
encoded_auth = base64.b64encode(auth_string.encode('utf-8')).decode('utf-8')
req = urllib.request.Request(
mailjet_url,
data=json.dumps(email_data).encode('utf-8'),
headers={'Content-Type': 'application/json', 'Authorization': f'Basic {encoded_auth}'},
method='POST'
)
with urllib.request.urlopen(req) as response:
pass
return (json.dumps({'status': 'success'}), 200, headers)
except Exception as e:
print(f"Execution Error: {str(e)}")
return (json.dumps({'error': 'Internal system error'}), 500, headers)