Help

Most questions are answered by the reference below, which is generated from the product itself and is never out of date. If it is not there, write to us.

Reference

• TrackingConnect a form or calendar on another platform so a submission joins the visitor who was already browsing.
• AutomationsEvery trigger that can start a flow and every action it can take.
• MetricsEvery number a dashboard widget can show, and which shapes it fits.
• Data fieldsEvery field type a Data table column can be, and what each one stores.
• IntegrationsEvery app SIGNL connects to, how it connects, and what it does once connected.
• WebhooksHave SIGNL call your URL when something happens: every event, the payload and how to verify it.
• EmbedsPut a SIGNL form or booker on your own site, with theming, identity handoff and a code sample.
• MCPConnect an MCP client to SIGNL over OAuth or an API key, what each scope allows, and every tool it can call.
• REST APIEvery tool as an HTTP endpoint: authentication, scopes, each tool's body fields and the errors, from the OpenAPI contract.
• ChangelogWhat's shipped in SIGNL, newest first.

Ask a person

• support@trysignl.appWrite to the team about anything else.
• Report BugIn the app sidebar once you are signed in. Describe what went wrong; it attaches a screenshot of the page, which you can remove before sending.
• Request FeatureIn the app sidebar once you are signed in. Say what would make SIGNL work better for you.
• Request an integrationName a tool SIGNL does not connect to yet. No account needed.
• Privacy, terms and your dataEmail mason@infoscalelab.com, the contact the privacy policy and terms give.

Four things that get you a useful answer first time:

• ·The workspace name in the sidebar, and the page you were on.
• ·What you expected to happen, and what happened instead.
• ·Roughly when it happened: a timestamp lets us find the exact request in the logs.
• ·A screenshot, if anything looked wrong rather than behaved wrong.

Reporting something that looks wrong on screen rather than broken? Say which theme you were in — light and dark are separate code paths and a defect in one is often fine in the other.