fix(flows): correct email template variable and add tiktok integration field - #554
Merged
Conversation
…n field
- Replace {{page_name}} with {{page_user_name}} in email step default footer
- Add tiktok case to getIntegrationField for inbox name resolution
- Add integrationTiktok to InboxWithIntegrations type
There was a problem hiding this comment.
Pull request overview
This PR fixes a broken email template variable and completes TikTok integration-name resolution in the variables system, ensuring {{page_user_name}} renders correctly across supported inbox channels.
Changes:
- Update the email step default footer template to use
{{page_user_name}}(valid system field) instead of the nonexistent{{page_name}}. - Add a missing
tiktokchannel case ingetIntegrationFieldto returninbox.integrationTiktok?.name. - Extend
InboxWithIntegrationsto includeintegrationTiktok, matchingInboxService.withIntegrationsand enabling correct typing for the new lookup.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/variables/src/helpers/integration-fields.ts | Adds TikTok channel handling so page_user_name resolves to the TikTok integration name. |
| packages/flow-config/src/steps/email.ts | Fixes the default email footer template variable to {{page_user_name}}. |
| packages/database/src/types.ts | Adds integrationTiktok to InboxWithIntegrations to support typed access in variable resolution. |
viethung0o0
pushed a commit
that referenced
this pull request
Sep 7, 2026
…n field (#554) - Replace {{page_name}} with {{page_user_name}} in email step default footer - Add tiktok case to getIntegrationField for inbox name resolution - Add integrationTiktok to InboxWithIntegrations type Co-authored-by: Deathgiver <anonymous@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
{{page_name}}→{{page_user_name}}in email step default footer templatetiktokcase togetIntegrationFieldso TikTok inbox names resolve correctly in variablesintegrationTiktoktoInboxWithIntegrationstype to support the field lookupChanges
packages/flow-config/src/steps/email.ts— correct variable name in unsubscribe footerpackages/variables/src/helpers/integration-fields.ts— addtiktokchannel casepackages/database/src/types.ts— extendInboxWithIntegrationswithintegrationTiktokTest plan
pnpm lintpnpm --filter @chatbotx.io/flow-config check-typespnpm --filter @chatbotx.io/variables check-typespnpm --filter @chatbotx.io/database check-types{{page_user_name}}