Skip to content

fix(integrations): remove outdated trigger mode text from FAQ#3739

Merged
waleedlatif1 merged 1 commit intostagingfrom
waleedlatif1/remove-trigger-mode-text
Mar 24, 2026
Merged

fix(integrations): remove outdated trigger mode text from FAQ#3739
waleedlatif1 merged 1 commit intostagingfrom
waleedlatif1/remove-trigger-mode-text

Conversation

@waleedlatif1
Copy link
Collaborator

Summary

  • Remove outdated "switch to Trigger mode" text from autogenerated integration FAQ
  • Updated to reflect current trigger block workflow

Type of Change

  • Bug fix

Testing

Tested manually

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel
Copy link

vercel bot commented Mar 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
docs Skipped Skipped Mar 24, 2026 1:47pm

Request Review

@cursor
Copy link

cursor bot commented Mar 24, 2026

PR Summary

Low Risk
Low risk copy-only change limited to autogenerated integration FAQ text; no functional logic or data handling is modified.

Overview
Updates the autogenerated integration FAQ answer for webhook-triggered workflows to remove outdated guidance about switching a block to Trigger mode and instead instruct users to add a dedicated ${name} trigger block before copying the webhook URL.

Written by Cursor Bugbot for commit bb2843f. Configure here.

@waleedlatif1 waleedlatif1 merged commit a783b9d into staging Mar 24, 2026
7 checks passed
@waleedlatif1 waleedlatif1 deleted the waleedlatif1/remove-trigger-mode-text branch March 24, 2026 13:47
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 24, 2026

Greptile Summary

This PR removes outdated UI copy from the autogenerated integration FAQ by replacing the stale "switch the ${name} block to Trigger mode" phrasing with the current "Add a ${name} trigger block to your workflow" wording, accurately reflecting how trigger blocks work in the current Sim UI.

  • Updates a single template string in buildFAQs() inside apps/sim/app/(landing)/integrations/[slug]/page.tsx
  • No logic, structure, or styling changes — purely a content correction
  • Improves accuracy for all integration pages that expose trigger-based FAQs (i.e., any integration where triggers.length > 0)

Confidence Score: 5/5

  • Safe to merge — isolated text-only fix with no risk to runtime behaviour.
  • The change is a single-line string update in a static FAQ builder. There are no logic changes, no new imports, no type changes, and no side effects. The updated phrasing correctly matches the current trigger block UX and removes the misleading "Trigger mode" reference.
  • No files require special attention.

Important Files Changed

Filename Overview
apps/sim/app/(landing)/integrations/[slug]/page.tsx Single-line FAQ answer text updated from "switch to Trigger mode" to "Add a [name] trigger block" to reflect current trigger block workflow — no logic or structural changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Integration page loaded] --> B{triggers.length > 0?}
    B -- No --> C[Skip trigger FAQ entries]
    B -- Yes --> D["FAQ: 'How do I trigger a Sim workflow?'"]
    D --> E["Answer: Add a {name} trigger block → copy webhook URL → paste into {name} settings"]
    E --> F["FAQ: 'What data does Sim receive when a {name} event fires?'"]
    F --> G[FAQ rendered on page + injected into FAQPage JSON-LD]
Loading

Reviews (1): Last reviewed commit: "fix(integrations): remove outdated trigg..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant