Intercom contact json slim for crm sidebar
Sidebar cards without full custom attributes
Intercom payloads are heavy for React. Contact id email and company for quick context. RealComposer output mapping returns only the fields your UI needs at the edge.
Why Intercom contact json slim for crm sidebar is hard without an edge proxy
Calling Intercom directly from React risks leaked secrets, CORS blocks, or oversized JSON that slows rendering.
- Exposed API keys in React bundles or DevTools
- Sequential upstream calls on slow mobile networks
- Third-party rate limits and surprise billing spikes
How RealComposer Solves This at the Edge
Store credentials in Secret Vault
Save INTERCOM_ACCESS_TOKEN in RealComposer.
Configure edge pipeline
Add upstream steps with vault header injection and map the response fields your client needs.
Call from React
Use your workspace edge URL with a restricted client token.
const res = await fetch('https://realcomposer.com/v1/workspace/slim-intercom-contact-json-sidebar', {
headers: { Authorization: 'Bearer rc_live_client_token' }
});
const data = await res.json();
{
"status": 200,
"debug_trace": "trace_batch2",
"data": {
"id": "obj_batch2",
"status": "active",
"audit_logs": [
{
"action": "fetch",
"timestamp": 1714589200
}
],
"internal_metadata": {
"cluster": "edge"
},
"result": {
"name": "Sample",
"tags": [
"batch2"
]
}
}
}
{
"id": "obj_batch2",
"status": "active",
"result": {
"name": "Sample",
"tags": [
"batch2"
]
}
}
curl -X GET "https://realcomposer.com/v1/workspace/slim-intercom-contact-json-sidebar" \ -H "Authorization: Bearer rc_live_client_token"
Developer Questions & Troubleshooting
Is it safe to call Intercom from React?
Only if secrets stay off the device. RealComposer injects credentials on the server edge so clients never hold production keys.
Does RealComposer add latency?
Cloudflare edge execution adds a few milliseconds; caching can answer repeat calls in under 10ms.
Deploy this React + Intercom Recipe
Clone this pre-configured pipeline into your RealComposer workspace in one click. We pre-populate upstream URLs, headers, and mapping rules.