You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! While evaluating self-hosted Warmbly (main at 91676e8) we hit a few gaps:
1. Cross-campaign duplicates.skip_active_in_other_campaigns only skips leads that are pending, active or paused in another live campaign (activeElsewhereClause, internal/repository/pg_contact.go:2348), so a contact who already replied to or finished another campaign is enrolled again. Linked-segment auto-enrolment ignores the option. Suggestion: an option to skip any contact already enrolled in another campaign of the workspace.
2. No AI_PROVIDER fallback for TypeSafe judgments. Bounce classification (internal/app/bounceclass/classify.go:78), inbox tagging including the removal-request suppression (cmd/consumer/main.go:513) and form triage (internal/app/form/triage.go:64) need a TypeSafe key, and TYPESAFE_ENDPOINT only helps with a TypeSafe-compatible server. With dsn.Blame in front this matters less for bounces, but tagging and triage are out of reach for self-hosters who only have an OpenAI-compatible provider.
3. The sequence notify node is a no-op.internal/repository/sequence_actions.go:22 accepts notify, but both executors fall through to an empty default (internal/tasks/campaign_task.go:1631, internal/app/advanced/reply_actions.go:415), while docs/content/docs/guides/sequences.mdx:214 says it "fires your webhooks and integrations". Either wire it (e.g. to automation.run or custom.event) or reject it and fix the docs.
Minor
A bare "stop" followed by a title/company line or a legal disclaimer doesn't opt out, because of the closed whitelist in optout_command.go.
An unplaced bounce (subject-only NDR, bare 554) drops the lead from its campaign, although the address is not suppressed.
An unknown GET /v1/unibox param (e.g. campaignId) is ignored and returns an unfiltered 200.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi! While evaluating self-hosted Warmbly (main at 91676e8) we hit a few gaps:
1. Cross-campaign duplicates.
skip_active_in_other_campaignsonly skips leads that are pending, active or paused in another live campaign (activeElsewhereClause,internal/repository/pg_contact.go:2348), so a contact who already replied to or finished another campaign is enrolled again. Linked-segment auto-enrolment ignores the option. Suggestion: an option to skip any contact already enrolled in another campaign of the workspace.2. No
AI_PROVIDERfallback for TypeSafe judgments. Bounce classification (internal/app/bounceclass/classify.go:78), inbox tagging including the removal-request suppression (cmd/consumer/main.go:513) and form triage (internal/app/form/triage.go:64) need a TypeSafe key, andTYPESAFE_ENDPOINTonly helps with a TypeSafe-compatible server. Withdsn.Blamein front this matters less for bounces, but tagging and triage are out of reach for self-hosters who only have an OpenAI-compatible provider.3. The sequence
notifynode is a no-op.internal/repository/sequence_actions.go:22acceptsnotify, but both executors fall through to an empty default (internal/tasks/campaign_task.go:1631,internal/app/advanced/reply_actions.go:415), whiledocs/content/docs/guides/sequences.mdx:214says it "fires your webhooks and integrations". Either wire it (e.g. toautomation.runorcustom.event) or reject it and fix the docs.Minor
optout_command.go.GET /v1/uniboxparam (e.g.campaignId) is ignored and returns an unfiltered 200.Thanks for the project!
All reactions