Advanced Payloads for Slack, Discord, and Telegram

Choose Advanced mode for a specific provider need

A useful notification must survive the values real respondents enter, not merely look polished with sample text. Choose Advanced mode only when a provider-specific structure materially improves the alert, then validate substitutions without giving answers control over JSON or routing.

Advanced means a different validated structure for each provider: Slack Block Kit, Discord embeds, or supported Telegram content and option fields. Compare Slack Block Kit blocks, Discord embed object, and Telegram Bot API for the provider-owned shapes and limits.

FormBeacon performs context-aware substitution in supported strings and rejects unknown fields, unsafe URLs, routing changes, and invalid provider shapes before delivery.

Use the hiring-application scenario consistently while testing: a fictional Platform Engineer applicant, reserved item IDs, reference SYN-1042, and a review link under https://review.example. Keeping one harmless scenario across providers makes serialization differences visible without confusing the comparison with different source data. It also makes failure isolation honest: when Basic, Rich, and Advanced receive the same synthetic values, a difference in outcome belongs to content handling or the provider rather than to the form response.

Record the mode, provider, synthetic reference, validation result, and visible destination outcome without copying the rendered message or provider response into an incident note. If one provider rejects the structure, keep the other destinations unchanged and correct only that provider's document. Failure isolation means a Discord embed error does not cause a Slack webhook rotation, a Telegram option failure does not justify recreating a Google trigger, and a valid Basic fallback remains available while the exact Advanced field is corrected.

Choose the format before writing the template

Build the notification message from the simplest reliable format

For provider-specific Advanced payloads, start with Basic mode. The variable picker includes form and response metadata plus every current form field keyed by stable Google item ID. Insert all fields creates provider-neutral rows; answer-based conditions and respondent-controlled routing remain unsupported.

The first message for provider-specific Advanced payloads should identify the form, state when the response was submitted, include only the information the first reader needs, and supply a stable response reference when useful. Put the action before decorative context. On a phone, the first few lines should explain why the alert matters without requiring the reader to expand a card or decode internal abbreviations.

Advanced mode in provider-specific Advanced payloads is provider-specific and schema validated. Variable substitution is context-aware and JSON safe, and respondent values remain text: they cannot become keys, object structure, credentials, destinations, template identity, or routing. Basic mode remains the most resilient choice when a workflow does not need provider-specific structure.

Prove Basic first

Save and test a Basic destination so credential, destination, and Google trigger failures are separate from Advanced validation.

Select the provider mode

Choose Slack Block Kit, Discord Embed, or Telegram Advanced. Do not paste a payload designed for another provider.

Start with the smallest schema

Add one static title and one supported text field, validate, save, and send a synthetic test.

Insert variables through the picker

Variables may appear only in documented strings. The editor retains stable item IDs even when field labels change.

Add a fixed-origin link

Enter an HTTPS template origin and place variables only in its path or query. FormBeacon URL-encodes each substituted value.

Exercise hostile punctuation

Use synthetic quotes, backslashes, newlines, angle brackets, mention-like text, emoji, and long values. The output must remain valid and inert.

Read the provider validation error

Correct the exact rejected field or limit. Do not rotate a working credential to respond to a schema error.

Keep a simpler fallback

Retain a known-good Basic or Rich version so an Advanced incident can be isolated without losing the destination configuration.

Formatting boundaries that affect real answers

• Advanced is available on Standard and Business for Slack, Discord, and Telegram; Free remains Basic only.
• Values cannot introduce object keys, arrays, credentials, endpoints, headers, template identity, or routing.
• Interactive Slack actions and Discord components are not implemented merely because a message can display a button.
• Provider acceptance does not prove a person read or acted on the message.

If provider-specific Advanced payloads requires a behavior listed here as a limit, do not hide the gap with copy or assume a future feature exists. Change the workflow, separate the forms, or choose a system that owns the missing behavior. Clear boundaries make setup and incident response easier.

Test with punctuation, blank fields, and long answers

To accept provider-specific Advanced payloads, run both a saved configuration test and a real form submission because they answer different questions. The saved test checks whether the current credential, destination, and message can reach the provider. A real submission additionally checks the Google trigger, form binding, response rendering, and delivery path. Both results must succeed.

1. 1Create a private test destination or tell the intended channel that a harmless test is coming.
2. 2Use a copied form with short fictional values, including one blank optional answer and one value containing punctuation.
3. 3Save the simplest supported mode first. Do not begin with a complex provider-specific Advanced structure.
4. 4Run the destination test and confirm a harmless notification at the intended destination.
5. 5Open the public responder view of the copied Google Form and submit it like a respondent would.
6. 6Confirm that exactly one new message appears, that the form title and submission time are plausible, and that the message is visible only to the intended audience.
7. 7Repeat once with a multiline answer and non-ASCII text. This catches formatting assumptions that a one-word test will miss.
8. 8Return to the add-on and review the visible delivery status without pasting credentials into a support conversation.

When checking provider-specific Advanced payloads, a working saved test and a failed real submission point to trigger ownership, Google authorization, the selected form, or event eligibility. If neither works, inspect the destination credential and provider permissions first. If delivery succeeds but the content is hard to read, keep the credential unchanged and simplify the template. Changing one layer at a time preserves evidence.

If provider-specific Advanced payloads still fails, use the provider-by-provider Google Forms notifications diagnostic guide. Record the test time, form name, destination name, and redacted error code. Never record submitted answers or the secret itself in a shared incident note.

Debug content separately from delivery

Understand where notification formatting is applied

In provider-specific Advanced payloads, Google invokes a user-owned installable form-submit trigger after configuration. The add-on reads the submitted response, renders the selected message, and sends it to FormBeacon's delivery API. The service applies plan limits and idempotency, uses the encrypted destination configuration to call the selected provider, and stores redacted delivery metadata rather than submitted answer content or rendered notification bodies.

That architecture is the diagnostic map for provider-specific Advanced payloads. FormBeacon is not a direct browser-to-webhook shortcut, and it does operate a delivery service. At the same time, response answers do not become a searchable FormBeacon database. Google Forms remains the record you inspect or correct; the provider receives the message you explicitly send; FormBeacon retains only the bounded configuration and redacted operational data required to deliver and diagnose it.

1. 1A respondent submits the Google Form and Google records the response.
2. 2The verified form owner’s installable trigger runs for that submission.
3. 3The add-on prepares a request containing the form and response references needed for delivery.
4. 4FormBeacon validates identity, form entitlement, quota, destination configuration, and idempotency.
5. 5The service calls the provider using the credential and destination required by the selected provider.
6. 6On success, the service records redacted success metadata and counts one successful outbound destination delivery as one notification.
7. 7On failure, the failed attempt does not consume the Free successful-delivery quota; an idempotent retry must not count the same delivery twice.

Before publishing provider-specific Advanced payloads, check provider behavior against the provider's current official documentation, because provider interfaces, permissions, limits, and policy wording can change. Check FormBeacon's product behavior and prices on the pricing page and in the current add-on rather than inferring them from an old screenshot.

Keep sensitive answers out of decorative messages

For provider-specific Advanced payloads, treat every webhook, bot token, and access token as a password. Restrict destination membership and rotate a credential after suspected disclosure.

Every delivery created by provider-specific Advanced payloads is a new copy of the notification. Google Form sharing does not automatically restrict a Slack channel, Discord channel, Telegram group, WhatsApp recipient, or webhook receiver. Before choosing Insert all fields, review every form question and assume every destination member can read the rendered values. For sensitive workflows, send a minimal reference and instruct authorized staff to open Google Forms rather than copying all answers into a notification.

• Use the narrowest private destination that still supports the workflow.
• Remove webhook URLs, bot tokens, access tokens, and real phone numbers from screenshots and screen recordings.
• Do not submit real customer or employee data while testing.
• Review provider retention, export, moderation, and member-access settings separately from FormBeacon.
• Rotate an exposed credential at the provider, update FormBeacon, and run both tests again.
• Delete test messages that contain even fictional data if they could confuse the operational channel later.

The privacy boundary for provider-specific Advanced payloads is specific: FormBeacon encrypts channel credentials and templates with versioned AES-256-GCM keys. It does not persist form answers, rendered notification bodies, raw provider payloads, OAuth or identity tokens, or complete billing webhook payloads. Retry storage in Google document properties is limited to form ID, response ID, idempotency key, and attempt count; the response is re-read from Google for a retry.

Those controls do not automatically make every form suitable for provider-specific Advanced payloads. You remain responsible for lawful collection, notices, consent where required, access control, retention at Google and the provider, and any industry-specific rules. This article explains product behavior and operational precautions; it is not legal advice.

Know which formats and destinations each plan supports

Before launching provider-specific Advanced payloads, match it to the pricing contract. Free supports one form, one active Basic destination on Slack, Discord, or Telegram, and 100 successful outbound destination deliveries per UTC calendar month. Standard supports up to 10 forms and Basic, Rich, and supported Advanced modes on Slack, Discord, and Telegram. Business adds WhatsApp approved templates, Webhook JSON, a shared 100-form workspace capacity, shared connectors, and unlimited explicitly invited workspace members.

For quota accounting in provider-specific Advanced payloads, one notification is one successful delivery to one outbound destination. If one response is sent to three active destinations and all three succeed, that is three successful deliveries. A failed delivery does not consume the Free quota, and an idempotent retry of the same delivery must not count twice. The Free counter resets lazily when the UTC month key changes; there is no reset cron to wait for.

Multiple destinations attached to provider-specific Advanced payloads use fan-out, not conditional routing. Every active destination on the form receives every eligible response. FormBeacon does not inspect an answer and select a destination, severity color, owner, or template branch. To keep different audiences separate, use separate forms or a workflow system that explicitly implements rules, and test that system with representative data.

Verify current FormBeacon amounts and included features for provider-specific Advanced payloads on the pricing page. Product prices and provider charges are different: Meta or another provider may apply its own usage charges, taxes, or policies, and those charges are not replaced by a FormBeacon subscription.

Maintain the template as the form changes

Treat provider-specific Advanced payloads like a small operational system. Name a form owner and a destination owner, document the purpose without recording secrets, and schedule a periodic harmless submission. Retest after changing form ownership, Google authorization, questions, destination membership, channel structure, webhook or bot settings, Meta templates, or the FormBeacon plan.

• Keep a copy of the intended message structure without any credential or real response data.
• Review whether every destination member still needs access to the notification content.
• Remove unused destinations before creating new ones so fan-out remains understandable.
• Use provider audit or administration features to investigate credential changes where available.
• When an owner leaves, deliberately transfer the Google Form and recreate or verify the user-owned trigger under the intended owner.
• During an incident, preserve timestamps and stable error codes, but redact identities, credentials, answers, and complete payloads.

The fallback for provider-specific Advanced payloads should remain visible: authorized staff can open Google Forms and inspect responses when chat delivery is delayed. Do not delete or mutate a form response simply because a notification failed. Repair the delivery path, make a harmless test, and use the response reference to reconcile operational action without copying the original answers into troubleshooting logs.