Integrations

Your own code does what you wrote. A third party does what it does today, which may differ from its documentation, from yesterday, and from its sandbox. This skill designs for that.

Analogy: an integration is a business partner in another time zone who answers by post. Letters arrive twice, out of order, or not at all, and sometimes the letter says "done" when nothing was done. You don't run the business on the letters — you keep your own books and reconcile.

Discovery (max 3 questions, only if unknown)

1. Direction — do you read from them, write to them, or both?
2. Do they push events (webhooks), or do you pull?
3. Is the connection per-product (one key of yours) or per-customer (each user connects their own account)?

Step 1 — Inbound: treat the webhook as a doorbell

Take only the id from the webhook, then fetch the object from their API with your own credentials. Never write the webhook body into your tables.

This one decision removes a family of problems: forged payloads, bodies re-serialized by a gateway (which breaks signature checks), events arriving out of order, and fields that are empty in the event but present in the API.