Separate triggered and blast campaign tools#30
Merged
Conversation
gmethvin
force-pushed
the
create-campaign-api
branch
from
5c58a8f to
75190be
Compare
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
1 participant
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.
This replaces the
create_campaigntool with two separate tools with more obvious behavior:create_and_schedule_campaign: Create a blast campaign to send tolistIdsat the providedsendAttime. Because this schedules the campaign it requires send permissions.create_triggered_campaign: Create a triggered campaign. This does not trigger a send so it only requires write permissions.These both use the
/api/campaigns/createendpoint but with different parameters. The goal is to make it even more obvious to the agent that it is creating and scheduling the blast campaign, making it less likely to assume that it's just creating a draft.