[Workflows] Use runtime data to choose which pipeline card to move and who to email
SubmittedWhat I want to do
As an admin, I want a workflow to:
- move an organization's existing card when the organization's tags change, including to a stage in another pipeline
- email the contact linked to a card when that card moves to a stage
Why
To keep exactly one card per organization across several pipelines, and to send stage-specific emails to each card's own contact. Today a workflow started by an organization can't reach that organization's existing card, so it can only create a second one. Send email can only go to a fixed address.
Proposed solution
- Move card to stage: let the Card field take runtime data, such as a card ID saved in an organization custom attribute or returned by an earlier step.
- Move card to stage: allow a stage in a different pipeline than the card's current one.
- Send email: allow the linked contact's primary email in the To field when a card starts the workflow, for example on Card moved to stage.
More details
- Today the Card field offers a fixed card, the card that started the workflow, or a card created earlier in the same workflow.
- The linked contact's fields can be used in Condition and Slack steps, but not in Send email.
- Update card fields and Archive card have the same Card field and should take runtime data too.
- A step that finds the card linked to an organization or contact would also solve the first case.
- Pipeline endpoints in the REST API would also solve this: see "[Pipeline] CSV import & API support".
Comments (0)
Sign in to post a comment.
No comments yet.