Receiving a notification does not mean the work is complete
A webhook delivers an event notification; polling checks for changes at defined intervals. Choosing between them requires reviewing the specific API's events, access, recovery and limits—not promising universal real-time behaviour. Think² organises collaborators with groups, context, the option for each collaborator to have its own computer, compatible models and authorised tools. This guide does not establish that Think² implements GitHub or Stripe endpoints or a tested integration.
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.
Situations to review
The required event is available and can be received securely
Evaluate webhooks with origin verification, provider-compliant acknowledgement and separate processing. GitHub documents a 2XX response within 10 seconds: a GitHub receipt requirement, not completion time for the entire task or a Think² SLA.
Distinguish received notification, prepared decision, approved action and verified execution. A 2XX response does not establish a business outcome.
The needed event is unavailable or current state needs checking
Evaluate periodic queries to the relevant resource. Before choosing an interval, confirm permissions, quotas, pagination, cursors, filters, available history and recovery after interrupted queries.
The choice follows endpoint documentation rather than an invented frequency or cost. A current-state query may miss intermediate transitions and does not establish the complete history.
Notifications are repeated or arrive out of order
Define event identity and scope, processing states, recovery and reconciliation with the source. Stripe documents duplicate deliveries and no guaranteed event order; do not generalise those conditions to every provider.
Do not repeat an action because a notification repeats, or infer current state from the last message received. Recording an ID alone does not establish atomic concurrency protection.
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.
How to evaluate the work
- Define the object, event, intended outcome and provider documentation. Distinguish event information from current state. Do not enable unnecessary events or grant access merely because a computer or endpoint exists.
- Choose event delivery, polling or both according to verifiable availability and recovery. For polling, document pagination, cursor advancement, filters and recovery periods. Do not claim a quota, window or interval without the specific API. No costs, load or latency were measured in this guide.
- Verify origin using the provider's mechanism and keep secrets out of URLs and logs. GitHub documents a 2XX response within 10 seconds; Stripe recommends a quick successful response before complex logic. Neither means accepting an invalid signature or guarantees persistent processing. If using a queue, verify reliable persistence before acknowledging: responding 2XX then losing the event does not establish recoverable receipt. These are implementation considerations, not a universal design or a claim about Think²'s implementation.
- Reusable template: provider/version; object/event; scope/ID; origin verification; receipt/evidence; processing state; duplicate/concurrency policy; cursor/recovery; current source/cutoff; proposal; external approval; execution/evidence. Fictional, unrun example: event EV7 for object S1 arrives twice, followed by late event EV6. Do not use arrival order as the current version. Preserve references, check the authorised source's state and prepare a reviewable decision. If EV7's outcome is unknown, do not treat ID seen as work completed or blindly repeat an action. Every external action requires prior, specific approval, even when triggered automatically. No webhook, polling, message or Think² integration was configured or tested; exactly-once execution was not established. Additional decision example, fictional and unrun: a provider documents an ‘order updated’ event but does not provide complete history; the assignment needs a current-state summary, not every transition. If an authorized endpoint can confirm that state, evaluate the event as a notification and a query for reconciliation. If no event exists but a queryable resource does, evaluate polling under its documented limits and recovery. Do not set a frequency without that documentation. If complete history is required and no source provides it, this design does not meet the requirement: preserve the gap. Proposed EV7/S1 record: received → persistence to be checked → outcome unknown. A duplicate EV7 neither authorizes another action nor establishes success; late EV6 does not become the current version by arriving later. A control row should separately identify receipt evidence, processing status and current source. This is not a webhook, queue, deduplication mechanism or query implemented by Think².
Frequently asked questions
Does a webhook mean the whole process finishes in real time?
No. HTTP receipt and later execution are different states. The requirements cited belong to each provider; they are not universal latency or a Think² performance promise.
Do all providers resend failed notifications?
Do not assume so. Stripe documents delivery attempts for up to three days in live mode and three sandbox retries over a few hours. Check the current policy and destination type before designing recovery; do not automatically apply it to GitHub or other services.
Do webhooks eliminate the need to query the API?
Queries may still be needed to confirm state or retrieve missing information. Verify endpoint access, quotas, pagination and history. Reading current state does not reconstruct every transition.
Sources and scope
- GitHub — Best practices for webhooks — Provider-specific or methodological reference, not proof of a Think² integration, performance or security guarantee.
- GitHub — Handling webhook deliveries — Provider-specific or methodological reference, not proof of a Think² integration, performance or security guarantee.
- Stripe — Webhooks — Provider-specific or methodological reference, not proof of a Think² integration, performance or security guarantee.
Keep exploring
- Organise administrative processes (Spanish)
- Approve external actions (Spanish)
- Control access and data (Spanish)
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.