Brian's Integration and Automation Notes
  • Welcome!
  • Allow Me to Brag a Bit
  • About
  • Integrations
    • ConnectWise Home
      • Authentication
      • API Documentation
  • Automations
    • Teams Notifications Azure Bot
      • Acknowledgement
      • Considerations
      • The Basics/Getting Started
        • Create a Response Handler Workflow in Rewst
        • Getting the IDs from Teams
      • Two Stage Message Process
        • Formatting the Initial Message
        • Getting the Message IDs
        • Formatting the Message Update
      • Formatting Action Buttons
        • Approve/Deny
        • Assign Resource to Ticket
      • Working with the Responses
      • System Incident/Maintance Notifications
        • Admitting Defeat on the Database
        • The Workflow Structure
      • Resources
    • Automated GitHub/GitBook Update Notifications
      • Prerequisites
      • 1. Set up a Basic Workflow
      • 2. Fork the GitHub Repository
      • 3. Set up Automatic Updates
      • 4. Set up notifications in GitHub
      • 5. Set up Remaining Workflow Actions
  • ConnectWise PSA Actions
    • About
    • Assigning Resources to Tickets
    • Ticket Assignment Note
    • Unbundle Ticket
    • Sales Activity Assignment Note
Powered by GitBook
On this page
  • Required Variables
  • Action
  • URL Path
  • Headers
  1. ConnectWise PSA Actions

Sales Activity Assignment Note

This action will add the assignment note and send it to the member. This action is not completed by the API when you add a resource to a sales activity.

Required Variables

  • member_id - The ID of the ConnectWise PSA member that you want to assign

  • activity_id - The ID of the service ticket that you are assigning the member to

  • assignment_note - The text note that you wish to include with the assignment. Regex in the body will handle replacing the spaces with '+'

  • member_email - The email address of the member you are assigning

  • member_first_name - The first name of the member you are assigning

  • member_last_name - The last name of the member you are assigning

  • member_identifier - The identifier of the member you are assigning. This can also be thought of as their PSA username such as tcat for Tom Cat.

  • existing_activity_note - The note added to the activity. You can either call this from a prior action in the workflow or return the notes attribute of the activity when you create or get it in the workflow.

  • assigner_identifier - The PSA username for the member that you want to use for the assignment. I utilize my API member for this.

Action

POST

URL Path

{ base URL including version identifier }/services/system_io/actionprocessor/Contact/SendStatusRequestFromActivityAction.rails

Headers

Key
Value

Content-Type

application/x-www-form-urlencoded

actionMessage=%7B%22payload%22%3A%22%7B%5C%22sendToMemberId%5C%22%3A{{ CTX.member_id }}%2C%5C%22soActivityRecId%5C%22%3A{{ CTX.task_id }}%2C%5C%22comments%5C%22%3A%5C%22{{ CTX.assignment_note }}%5C%22%2C%5C%22emailAddress%5C%22%3A%5C%22{{ CTX.member_email|urlencode }}%5C%22%2C%5C%22existingNotes%5C%22%3A%5C%2{{ CTX.existing_activity_note|regex_replace(' ','+')}}%5C%22%2C%5C%22memberID%5C%22%3A%5C%22{{ CTX.assigner_identifier }}%5C%22%2C%5C%22memberName%5C%22%3A%5C%22{{ CTX.member_first_name }}+{{ CTX.member_last_name }}%5C%22%2C%5C%22requestType%5C%22%3A%5C%22new%5C%22%2C%5C%22resourceID%5C%22%3A%5C%22{{ CTX.member_identifier }}%5C%22%2C%5C%22documentRecIds%5C%22%3A%5B%5D%7D%22%2C%22payloadClassName%22%3A%22SendStatusRequestFromActivityAction%22%2C%22project%22%3A%22ContactCommon%22%7D
PreviousUnbundle Ticket

Last updated 7 months ago