Integrations
Discord and webhook notifications
Send Shopify app activity to Discord or Grok Bot and look up the delivered information through analytics SQL.
Last updated
In hosted Fusionmetrics, open Settings → Integrations as an Organization admin. You can connect one Discord channel and one generic HTTPS webhook alongside your Slack destinations. Each destination can follow all Apps or one App. Select installs, uninstalls, trials, subscriptions, or App Store reviews independently.
Connect a destination
For Discord, copy the channel webhook URL from Server Settings → Integrations → Webhooks and paste it into the Discord form. Discord receives a message with the App, activity, and available Merchant details. Discord webhook guide
For Grok Bot, add a webhook trigger to the routine. Paste its POST to URL and key into the generic webhook form. Fusionmetrics sends the key in the HTTP Authorization: Bearer header. A generic endpoint can also accept the JSON without a bearer key. Grok Bot routine webhooks
Open Preview connection test before saving. Test and connect makes a real request, which starts a Grok Bot routine. Only the synthetic test payload is sent during setup. A Grok Bot HTTP 200 confirms it started the run. Check the Bot’s chat for the result.
New and re-enabled destinations start with new activity. Replacing a URL sends a test and requires re-entering any bearer key. Delivery status and retries are per destination. If a request times out after the receiver accepts it, the receiver can see a retry. Use the JSON event id to deduplicate.
Look up a Merchant
Select the individual App in the analytics MCP and use run_sql with the Merchant’s shop domain. This works as soon as any configured destination confirms delivery, including before the Merchant appears in the next dashboard refresh.
SELECT shop_name, current_review_history, latest_install_alert, latest_alert
FROM merchant_lookup
WHERE myshopify_domain = 'example.myshopify.com'
latest_alert and latest_install_alert contain the same versioned JSON sent to the generic webhook. Each includes the event ID and type, timestamps, App, source facts, and the enrichment available at delivery. The latest install remains available after an uninstall or billing change. Current review history can change later. Check its status and observation dates before interpreting counts.
For an earlier delivery or a review with no known shop domain, look up the event ID in the same App using SQL.
SELECT payload FROM merchant_alerts WHERE event_id = 'example-event-id'
The lookup covers confirmed deliveries recorded after this feature was enabled. Connection tests stay out of the lookup.