@awell-health/awell-extensions 2.0.196 → 2.0.198

package/dist/extensions/markdown.json

@@ -60,7 +60,7 @@
     "changelog": "# Dropbox Sign changelog"
   },
   "elation": {
-    "readme": "---\ntitle: Elation\ndescription: Elation is a cloud-based health record system designed for healthcare providers, clinics, and medical practices.\n---\n# Elation\n\nElation is a cloud-based health record system designed for healthcare providers, clinics, and medical practices. It offers a range of features including patient scheduling, charting, e-prescribing, billing, and telemedicine. Overall, Elation is designed to streamline the workflow of medical practices, improve patient care, and increase efficiency.\n\n## Setup\n\n### Webhooks\n\nThe integration of webhooks with Elation presents unique challenges and considerations:\n\n- **Non-Discriminative Triggers**: Elation does not differentiate between the creation or update of a resource. Both actions will set off webhook with action `saved`, which might not provide enough discriminative information for some use cases.\n- **Programmatic Setup**: Elation webhooks can only be configured programmatically, as there's no dedicated user interface in Elation to set up webhooks. View [this demo video](https://youtu.be/v8u6E8MEI8E) for a step-by-step guide on how to set up your webhooks in Elation.\n- **Limitation on user-triggered actions**: Elation has a concept called \"Preventing echo\". This means that that any action carried out by the user affiliated with the API credentials that created the subscription doesn't trigger a webhook. You can read more about this behaviour [here](https://docs.elationhealth.com/reference/webhooks). If you are not receiving any webhooks from Elation after setting up your subscription, then this is the reason. A feasible workaround to the above limitation is creating a dedicated user not meant for human interactions but serves the sole purpose of facilitating M2M communication.\n\nIf you need help setting up your webhooks in Elation, reach out! We are happy to help you.\n\n### Extension settings\n\nIn order to use this extension you will need to provide the extension with the following settings:\n\n- Base URL / endpoint URL of the API\n- Authorization URL\n- Client ID for OAuth2 Password authentication\n- Client Secret for OAuth2 Password authentication\n- API Username for OAuth2 Password authentication\n- API Password for OAuth2 Password authentication\n\nNot sure where you can find all of this information? Click [here](https://docs.elationhealth.com/reference/introduction) to have a look at Elation's Developer documentation.\n\n## Actions\n\nThe following actions are supported with Elation today:\n\n### Create Patient\n\nThis action creates a patient in Elation.\n\n**When creating a patient, you will have to specifiy the primary physician and caregiver practice ID:**\n- Primary physician ID: you can retrieve this ID by using the [Find Physicians](https://docs.elationhealth.com/reference/find-physicians) API call, or by using the `Find Physician` action\n- Caregiver Practice ID: similar to the primary physician ID, you can find this ID by using the same API call or action\n\n### Get Patient\n\nUsing a patient identifier, retrieve a patient object from Elation. \n\nNote that when retrieve the mobile phone number, we are tranforming the number to an international format. We apply a heuristic and assume all mobile numbers in Elation are in US national format so we prepend the number with the +1 country code. Having the number in international format unlocks more powerful functionality like sending text messages with 3rd party services like Twilio and MessageBird.\n\n### Update Patient\n\nUpdate a patient in Elation using any fields available in create patient. We use Elation's `PATCH` method to apply partial modifications to a the patient resource (i.e. update only what is needed).\n\n### Create Appointment\n\nEasily create a patient appointment in Elation.\n\nCreating an appointment requires a few strings to be well-formulated:\n- `Scheduled date` must be a datetime string (ISO-8601). For example, January 1, 2023 at noon, Pacific Time (-8 hours) would be shown as such: `2023-01-01T12:00:00.000-08:00`\n- `Reason` must not be free text. This value comes from the following list of appointment types (`Follow-Up`, `Office Visit`, `Physical Exam`, etc.):\n![Appointment types](./assets/elation-appointment-reason.png?raw=true \"Elation Appointment Types\")\n- `Patient` is the patient ID.\n- `Physician` is the physician ID (see `Find Physician`)\n- `Practice` is the practice ID (again, see `Find Physician`)\n\nYou can also include a duration (default to 15 minutes, or whatever has been set in your EHR)\n\n### Get Appointment\n\nRetrieve appointment details using an appointment ID. \n\n### Create Non-Visit Note\n\nThe non-visit note is a special kind of note that, as the name suggests, is not associated with a visit. These notes, in their simplest form, provide a chronological account of information about the patient.\n\n**Additional documentation for some of the action fields:**\n1. Category: The default category is \"Problem\" but you can choose any of \"Past\", \"Family\", \"Social\", \"Instr\", \"PE\", \"ROS\", \"Med\", \"Data\", \"Assessment\", \"Test\", \"Tx\", \"Narrative\", \"Followup\", \"Reason\", \"Plan\", \"Objective\", \"Hpi\", \"Allergies\", \"Habits\", \"Assessplan\", \"Consultant\", \"Attending\", \"Dateprocedure\", \"Surgical\", \"Orders\", \"Referenced\", \"Procedure\".\n2. Chart and document date automatically get set to the current date, i.e. the date when the action is orchestrated.\n\n### Delete Non-Visit Note\n\nDeletes the non-visit note identified by an ID.\n\n### Get Non-Visit Note\n\nRetrieve the details of a non-visit note identified by an ID.\n### Get physician\n\nUsing a physician identifier, retrieve a physician object from Elation.\n\n### Find physicians\n\nSearch a physician based on a set of parameters. The ID of the physician matching the search parameters will be returned. To retrieve the details of the physician, you can use the the \"Get physician\" action.\n\nNote that this action can only support finding one physician so if your search criteria match multiple physicians the action will throw an error.\n\n### ✨ Find Future Appointment\n\nTries to find a **single future appointment** for a patient based on a prompt in natural language. These are the steps executed by the action:\n\n1. All future appointments with status `Scheduled` or `Confirmed` for the patient are retrieved from Elation.\n2. Based on the provided prompt, an LLM tries to find a single appointment from the list of future appointments that matches the prompt.\n3. If multiple appointments exist that match the instructions, only the first one is returned.\n\nIf a matching appointment is found, the action returns the full appointment resource and an explanation of why the LLM chose this appointment.\n\n### ✨ Find Appointments\n\nTries to find **all appointments** for a patient based on a prompt in natural language. These are the steps executed by the action:\n\n1. All appointments, independent their date or status, for the patient are retrieved from Elation.\n2. Based on the provided prompt, an LLM tries to find all appointments from the list appointments that matches the prompt.\n\nThe action returns the full appointment resources of all appointments matching the prompt and an explanation of why the LLM chose these appointments. Additionally, the action returns a count of appointments by status.\n\nExample data points output below.\n\nAppointments (note: only displaying a partial appointment resource)```json\n[\n  {\n    \"id\": 456,\n    \"scheduled_date\": \"2023-07-12T20:44:22Z\",\n    \"status\": {\n      \"status\": \"Scheduled\",\n    },\n  },\n  {\n    \"id\": 456,\n    \"scheduled_date\": \"2023-08-12T20:44:22Z\",\n    \"status\": {\n      \"status\": \"Confirmed\",\n    },\n  }\n]```\n\nAppointment counts by status\n```json\n{\n  \"Scheduled\": 1,\n  \"Confirmed\": 1,\n}\n```\n\n### ✨ Update Patient Tags\n\nUses AI to manage patient tags in Elation based on natural language instructions. The action executes the following steps:\n\n1. Retrieves existing patient tags from Elation\n2. Uses an LLM to interpret natural language instructions and determine required tag changes\n3. Updates patient tags in Elation according to the interpreted changes\n\nThe action returns:\n- Complete list of updated tags after changes\n- Detailed explanation of what changes were made and why\n\n**Important Notes:**\n- When adding new tags, specify them in single quotes (e.g., 'Diabetes', 'High-Risk'). Tags must exist in your Elation database\n- Due to Elation API limitations, clearing all tags is implemented by setting a single space tag (' '). This is the recommended workaround from Elation's team\n\n### ✨ Cancel appointments\n\nGiven a prompt, this action retrieves a patient's upcoming appointments matching the prompt and cancels them.\n",
+    "readme": "---\ntitle: Elation\ndescription: Elation is a cloud-based health record system designed for healthcare providers, clinics, and medical practices.\n---\n# Elation\n\nElation is a cloud-based health record system designed for healthcare providers, clinics, and medical practices. It offers a range of features including patient scheduling, charting, e-prescribing, billing, and telemedicine. Overall, Elation is designed to streamline the workflow of medical practices, improve patient care, and increase efficiency.\n\n## Setup\n\n### Webhooks\n\nThe integration of webhooks with Elation presents unique challenges and considerations:\n\n- **Non-Discriminative Triggers**: Elation does not differentiate between the creation or update of a resource. Both actions will set off webhook with action `saved`, which might not provide enough discriminative information for some use cases.\n- **Programmatic Setup**: Elation webhooks can only be configured programmatically, as there's no dedicated user interface in Elation to set up webhooks. View [this demo video](https://youtu.be/v8u6E8MEI8E) for a step-by-step guide on how to set up your webhooks in Elation.\n- **Limitation on user-triggered actions**: Elation has a concept called \"Preventing echo\". This means that that any action carried out by the user affiliated with the API credentials that created the subscription doesn't trigger a webhook. You can read more about this behaviour [here](https://docs.elationhealth.com/reference/webhooks). If you are not receiving any webhooks from Elation after setting up your subscription, then this is the reason. A feasible workaround to the above limitation is creating a dedicated user not meant for human interactions but serves the sole purpose of facilitating M2M communication.\n\nIf you need help setting up your webhooks in Elation, reach out! We are happy to help you.\n\n### Extension settings\n\nIn order to use this extension you will need to provide the extension with the following settings:\n\n- Base URL / endpoint URL of the API\n- Authorization URL\n- Client ID for OAuth2 Password authentication\n- Client Secret for OAuth2 Password authentication\n- API Username for OAuth2 Password authentication\n- API Password for OAuth2 Password authentication\n\nNot sure where you can find all of this information? Click [here](https://docs.elationhealth.com/reference/introduction) to have a look at Elation's Developer documentation.\n\n## Actions\n\nThe following actions are supported with Elation today:\n\n### Create Patient\n\nThis action creates a patient in Elation.\n\n**When creating a patient, you will have to specifiy the primary physician and caregiver practice ID:**\n- Primary physician ID: you can retrieve this ID by using the [Find Physicians](https://docs.elationhealth.com/reference/find-physicians) API call, or by using the `Find Physician` action\n- Caregiver Practice ID: similar to the primary physician ID, you can find this ID by using the same API call or action\n\n### Get Patient\n\nUsing a patient identifier, retrieve a patient object from Elation. \n\nNote that when retrieve the mobile phone number, we are tranforming the number to an international format. We apply a heuristic and assume all mobile numbers in Elation are in US national format so we prepend the number with the +1 country code. Having the number in international format unlocks more powerful functionality like sending text messages with 3rd party services like Twilio and MessageBird.\n\n### Update Patient\n\nUpdate a patient in Elation using any fields available in create patient. We use Elation's `PATCH` method to apply partial modifications to a the patient resource (i.e. update only what is needed).\n\n### Create Appointment\n\nEasily create a patient appointment in Elation.\n\nCreating an appointment requires a few strings to be well-formulated:\n- `Scheduled date` must be a datetime string (ISO-8601). For example, January 1, 2023 at noon, Pacific Time (-8 hours) would be shown as such: `2023-01-01T12:00:00.000-08:00`\n- `Reason` must not be free text. This value comes from the following list of appointment types (`Follow-Up`, `Office Visit`, `Physical Exam`, etc.):\n![Appointment types](./assets/elation-appointment-reason.png?raw=true \"Elation Appointment Types\")\n- `Patient` is the patient ID.\n- `Physician` is the physician ID (see `Find Physician`)\n- `Practice` is the practice ID (again, see `Find Physician`)\n\nYou can also include a duration (default to 15 minutes, or whatever has been set in your EHR)\n\n### Get Appointment\n\nRetrieve appointment details using an appointment ID. \n\n### Create Non-Visit Note\n\nThe non-visit note is a special kind of note that, as the name suggests, is not associated with a visit. These notes, in their simplest form, provide a chronological account of information about the patient.\n\n**Additional documentation for some of the action fields:**\n1. Category: The default category is \"Problem\" but you can choose any of \"Past\", \"Family\", \"Social\", \"Instr\", \"PE\", \"ROS\", \"Med\", \"Data\", \"Assessment\", \"Test\", \"Tx\", \"Narrative\", \"Followup\", \"Reason\", \"Plan\", \"Objective\", \"Hpi\", \"Allergies\", \"Habits\", \"Assessplan\", \"Consultant\", \"Attending\", \"Dateprocedure\", \"Surgical\", \"Orders\", \"Referenced\", \"Procedure\".\n2. Chart and document date automatically get set to the current date, i.e. the date when the action is orchestrated.\n\n### Delete Non-Visit Note\n\nDeletes the non-visit note identified by an ID.\n\n### Get Non-Visit Note\n\nRetrieve the details of a non-visit note identified by an ID.\n### Get physician\n\nUsing a physician identifier, retrieve a physician object from Elation.\n\n### Find physicians\n\nSearch a physician based on a set of parameters. The ID of the physician matching the search parameters will be returned. To retrieve the details of the physician, you can use the the \"Get physician\" action.\n\nNote that this action can only support finding one physician so if your search criteria match multiple physicians the action will throw an error.\n\n### ✨ Find Future Appointment\n\nTries to find a **single future appointment** for a patient based on a prompt in natural language. These are the steps executed by the action:\n\n1. All future appointments with status `Scheduled` or `Confirmed` for the patient are retrieved from Elation.\n2. Based on the provided prompt, an LLM tries to find a single appointment from the list of future appointments that matches the prompt.\n3. If multiple appointments exist that match the instructions, only the first one is returned.\n\nIf a matching appointment is found, the action returns the full appointment resource and an explanation of why the LLM chose this appointment.\n\n### ✨ Find Appointments\n\nTries to find **all appointments** for a patient based on a prompt in natural language. These are the steps executed by the action:\n\n1. All appointments, independent their date or status, for the patient are retrieved from Elation.\n2. Based on the provided prompt, an LLM tries to find all appointments from the list appointments that matches the prompt.\n\nThe action returns the full appointment resources of all appointments matching the prompt and an explanation of why the LLM chose these appointments. Additionally, the action returns a count of appointments by status.\n\nExample data points output below.\n\nAppointments (note: only displaying a partial appointment resource)```json\n[\n  {\n    \"id\": 456,\n    \"scheduled_date\": \"2023-07-12T20:44:22Z\",\n    \"status\": {\n      \"status\": \"Scheduled\",\n    },\n  },\n  {\n    \"id\": 456,\n    \"scheduled_date\": \"2023-08-12T20:44:22Z\",\n    \"status\": {\n      \"status\": \"Confirmed\",\n    },\n  }\n]```\n\nAppointment counts by status\n```json\n{\n  \"Scheduled\": 1,\n  \"Confirmed\": 1,\n}\n```\n\n### ✨ Update Patient Tags\n\nUses AI to manage patient tags in Elation based on natural language instructions. The action executes the following steps:\n\n1. Retrieves existing patient tags from Elation\n2. Uses an LLM to interpret natural language instructions and determine required tag changes\n3. Updates patient tags in Elation according to the interpreted changes\n\nThe action returns:\n- Complete list of updated tags after changes\n- Detailed explanation of what changes were made and why\n\n**Important Notes:**\n- When adding new tags, specify them in single quotes (e.g., 'Diabetes', 'High-Risk'). Tags must exist in your Elation database\n- Due to Elation API limitations, clearing all tags is implemented by setting a single space tag (' '). This is the recommended workaround from Elation's team\n\n### ✨ Check Patient Tags\n\nUses AI to check if a patient's tags match given instructions in natural language. The action executes the following steps:\n\n1. Retrieves existing patient tags from Elation\n2. Uses an LLM to interpret natural language instructions and check if the patient's tags match the requirements\n3. Returns a boolean result and explanation of the check\n\nThe action returns:\n- `tagsFound`: Boolean indicating if the patient's tags match the instructions\n- `explanation`: Detailed explanation of why the tags match or don't match the instructions\n\n\n**Important Notes:**\n- When specifying exact tag matches, use double quotes (e.g., \"Diabetes\", \"High-Risk\"). Tags must exist in your Elation database\n- The LLM can understand complex logical conditions like \"either/or\", \"both\", \"not\", \"any of\", \"none of\"\n\n### ✨ Cancel appointments\n\nGiven a prompt, this action retrieves a patient's upcoming appointments matching the prompt and cancels them.\n",
     "changelog": "# Elation Changelog\n\n## January 30, 2024\n\n- New actions\n  - Post letter: Using patient and practice identifier, post a new letter to either Provider, Patient or associate it with an existing Referral.\n\n## October 3, 2023\n\n- The README is now more concise with less unneeded detail. A section on the particularities of Elation subscriptions (webhooks) was added.\n- Misc. updates to labels, descriptions, action fields order\n- Action updates\n  - Create Non-Visit Note:\n    - Simplify the action by removing some optional action fields (we can always expand later)\n    - `document_date` and `chart_date` are now automatically set to the date of today so that the corresponding action fields could be removed\n  - Create patient\n    - `dob` is now a `date` field type (was a string)\n    - You can pass a mobile phone number and email when creating a patient\n  - Find physician\n    - Only returns the physician ID instead of all the details of the physician. To retrieve the details one can use the new `Get physician` action\n  - Update patient\n    - `dob` is now a `date` field type (was a string)\n    - We are now using `PATCH` instead of `PUT` which allows for a partial update, i.e. only update the fields that are needed.\n- New actions\n  - Get physician: Using a physician identifier, retrieve a physician object from Elation.\n- Removed actions\n  - Update Non-Visit Note\n- Webhooks\n  - Fix the type of `patientId` in `patientCreatedOrUpdated` webhook\n  - Added `appointmentCreatedOrUpdated` webhook\n\n## September 4, 2023\n\n- rename `onCreatePatient` webhook to `patientCreatedOrUpdated`\n- filter non `saved` actions for this webhook\n\n## August 21, 2023\n\n- make non-visit note text a large input (`StringType.TEXT`)\n\n## May 23, 2024\n\n- add patient_status.status to patient object in getPatient action\n- add status to updatePatient action\n"
   },
   "epic": {
@@ -163,6 +163,10 @@
     "readme": "---\ntitle: Talkdesk\ndescription: Talkdesk is a cloud-based customer experience and contact center software company. It provides a platform that enables businesses to set up and manage their customer service and support operations.\n---\n# TalkDesk\n\nTalkdesk is a cloud-based customer experience and contact center software company. It provides a platform that enables businesses to set up and manage their customer service and support operations. Talkdesk offers a range of features and tools to streamline and enhance communication between businesses and their customers.\n\n## Setup\n\nTo set up the extension, you'll need your Talkdesk account name along with a client ID and client secret. Please ensure that the credentials you provide are associated with the necessary permissions, or \"scopes,\" to run the extension:\n\n- flows-interactions:start\n\n## Custom Actions\n\n### Trigger flow\n\nEnables the initiation of a Talkdesk flow directly from an Awell careflow. This feature triggers an interaction using the most recent published version of a specific Studio flow. You'll need to supply the ID of the flow and the data (as a JSON object) that you want to input into the flow.\n\nImportant: Please note that Talkdesk sets a restriction of up to two API requests per second (rps) for each account using their Flows API.\n\n[Click here](https://studio.talkdesk.com/docs/sending-notifications-to-contacts-via-api-request) to learn more about triggering flows via the Talkdesk API and here to read the [API docs](https://docs.talkdesk.com/reference/flows-api-ref).\n",
     "changelog": "# TalkDesk changelog\n"
   },
+  "text-em-all": {
+    "readme": "---\ntitle: Text-Em-All\ndescription: Text-Em-All is a texting and automated calling service that enables organizations to communicate with patients.\n---\n\n# Text-Em-All\n\nText-Em-All is a texting and automated calling service that enables organizations to communicate with patients.\n\n## Supported Actions\n\n- **sendSMSBroadcast** - Schedule SMS message to a specified user\n- **sendCallBroadcast** - Schedule an Call message to a specified user\n\n## Webhooks\n\n# Broadcast Status Change\n\nTriggered when the status of a call or text broadcast changes to one of the following states:\n\n| Status | Description |\n|--------|-------------|\n| `created` | A broadcast has been created on your Call-Em-All account. It may be scheduled to run in the future and it may not have all the information set up to run yet. |\n| `ready` | The broadcast has all information necessary to run and is waiting for its start time. |\n| `broadcasting` | The broadcast started to send out phone calls or text messages. |\n| `completed` | The broadcast has finished sending out all phone calls or text messages. |\n| `paused` | The broadcast has been paused and no calls or texts are going out. |\n| `resumed` | A paused broadcast resumes. |\n| `canceled` | The broadcast was canceled. |\n| `expired` | The window that was set up for the broadcast by the user was insufficient to send out all the calls or texts. The broadcast has been expired and some of the calls and texts are not delivered. |\n\nWebhook includes:\n- Broadcast ID\n- Broadcast status\n\n## Setup\n\nThe Text-Em-All extension requires the following settings to be configured:\n\n| Setting name | Required | Description |\n|--------------|----------|-------------|\n| `customerKey` | Yes | Your Text-Em-All customer key |\n| `customerSecret` | Yes | Your Text-Em-All customer secret |\n| `token` | Yes | Your Text-Em-All token |\n| `baseUrl` | Yes | Your Text-Em-All base URL |\n\n# Find out more\n\nFor detailed information about setting up webhooks, notification formats, and additional event types, please visit the [Text-Em-All Webhooks documentation](https://dev.text-em-all.com/Webhooks#events).",
+    "changelog": "# Text-em-all changelog\n"
+  },
   "textline": {
     "readme": "---\ntitle: TextLine\ndescription: Textline's business texting software offers solutions for sales, marketing, customer service and beyond. Utilize the power of SMS to grow quickly.\n---\n\n# TextLine\n\nTextLine is a customer engagement platform used by hundreds of thousands of businesses and more than ten million developers worldwide to build unique, personalized experiences for their customers.\n\nThey are known for democratizing channels like voice, text, chat, video, and email through APIs, making it easy for every organization to build meaningful interactions with customers on the channels they prefer.\n\n## Extension settings\n\nIn order to set up this extension, you will need:\n\n1. A TextLine API key or auth token which can be found in the TextLine console.\n2. Your account SID which can be found in the TextLine console.\n3. A phone number to send the message from. This must be a TextLine phone number that you own.\n\n## Custom Actions\n\n### Send SMS\n\nSend an SMS with TextLine to a recipient of your liking.\n\n### Get messages\n\nThis action retrieves received messages. One can apply the `phoneNumber` filter to this action to display only received messages from that `phoneNumber`.\nOnly the last 30 messages are returned.\n\n### Set Contact Consent\n\nFor HIPAA and Pro accounts setup with Contact Consent, this action can set contact's consent status. To do this, your account must have API import allowed and the user making the API request must have the \"Can manually set consent\" permission on for their role. You must then use the Contact's phone number and their consent status (true or false).\n\n#### Simple Use Case\n\n**Initiating a Conversation**: A user sends a message to \"Number A\", initiating a conversation.\n\n**Receiving a Response**: \"Number A\" responds to the message, contributing to the ongoing conversation.\n\n**Searching Messages & Applying Filters**: To focus on the responses from \"Number A\", `phoneNumber`` filter can be applied to only show received messages from \"Number A\" within the conversation. This allows users to easily review and manage responses from \"Number A\", without the clutter of other received messages.\n\n",
     "changelog": "# TextLine changelog\n\n## 2024-03-11\n\n1. Add option to set department ID when sending messages and when retrieving messages. Check official documentation here: https://textline.docs.apiary.io/#reference/conversations/phone-numbers/message-a-phone-number\n## 2024-03-5\n\n1. Add capability to set contact consent status (https://textline.docs.apiary.io/#reference/customers/set-contact-consent/set-contact-consent)\n2. Add several fixes and tweaks to improve current actions\n\n## 2024-02-26\n\n1. Add capability to search for messages using all the allowed filters provided by TextLine API.\n2. Add \"Send SMS\" action\n"

package/dist/extensions/text-em-all/actions/createCallBroadcast/__testdata__/CreateCallBroadcast.mock.d.ts

@@ -0,0 +1,88 @@
+export declare const CreateCallBroadcastMockResponse: {
+    status: number;
+    statusText: string;
+    headers: {
+        Location: string;
+    };
+    data: {
+        Uri: string;
+        UriBroadcastDetails: string;
+        BroadcastID: number;
+        BroadcastName: string;
+        BroadcastType: string;
+        BroadcastStatus: string;
+        BroadcastStatusCategory: string;
+        CreatedDate: string;
+        StartDate: string;
+        CompletedDate: null;
+        CallerID: string;
+        CreditsUsed: null;
+        MaxCreditCost: number;
+        PhoneNumberCount: number;
+        TotalCompleted: number;
+        User: {
+            PinCode: null;
+            UserID: number;
+            UserName: null;
+            FirstName: null;
+            LastName: null;
+            Email: null;
+            Phone: null;
+            CallerID: null;
+            IsMasterUser: boolean;
+            AuthToken: null;
+            State: null;
+            Permissions: null;
+        };
+        TransferAndConnect: {
+            IsTransfer: boolean;
+            TransferLines: number;
+            TransferNumber: string;
+            TransferCreditsUsed: null;
+        };
+        Audio: {
+            Uri: string;
+            AudioID: string;
+            Name: null;
+            Description: null;
+            Favorite: null;
+            Shared: null;
+            Length: number;
+            MessageType: null;
+            ReadOnly: null;
+            Created: null;
+            LastUsed: null;
+            TextToSpeech: boolean;
+        };
+        AudioVM: {
+            Uri: string;
+            AudioID: string;
+            Name: null;
+            Description: null;
+            Favorite: null;
+            Shared: null;
+            Length: number;
+            MessageType: null;
+            ReadOnly: null;
+            Created: null;
+            LastUsed: null;
+            TextToSpeech: boolean;
+        };
+        RetryTimes: number;
+        CallThrottle: number;
+        LivePersonTotal: number;
+        AnsweringMachineTotal: number;
+        BusyNoAnswerTotal: number;
+        InvalidNumberTotal: number;
+        SurveyResponseTotal: number;
+        TransferTotal: number;
+        SurveyResponses: null;
+        MaxMessageLength: number;
+        MessageRecordingInstruction: null;
+        EstimatedDuration: number;
+        EstimatedCompletion: null;
+        ExcludedDaysIgnored: boolean;
+        CallingWindowIgnored: boolean;
+        NotEnoughTimeToComplete: boolean;
+    };
+};

package/dist/extensions/text-em-all/actions/createCallBroadcast/__testdata__/CreateCallBroadcast.mock.js

@@ -0,0 +1,92 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CreateCallBroadcastMockResponse = void 0;
+exports.CreateCallBroadcastMockResponse = {
+    status: 200,
+    statusText: 'OK',
+    headers: {
+        Location: 'https://staging-rest.call-em-all.com/v1/broadcasts',
+    },
+    data: {
+        Uri: '/v1/broadcasts/10006607',
+        UriBroadcastDetails: '/v1/broadcasts/10006607/details',
+        BroadcastID: 10006607,
+        BroadcastName: 'Testing Alert System with Transfer Option',
+        BroadcastType: 'Announcement',
+        BroadcastStatus: 'AuthorizationApproved',
+        BroadcastStatusCategory: 'Scheduled',
+        CreatedDate: '2020-11-20 14:04:09-0600',
+        StartDate: '2020-11-20 14:04:08-0600',
+        CompletedDate: null,
+        CallerID: '2142960678',
+        CreditsUsed: null,
+        MaxCreditCost: 1,
+        PhoneNumberCount: 1,
+        TotalCompleted: 0,
+        User: {
+            PinCode: null,
+            UserID: 215790,
+            UserName: null,
+            FirstName: null,
+            LastName: null,
+            Email: null,
+            Phone: null,
+            CallerID: null,
+            IsMasterUser: false,
+            AuthToken: null,
+            State: null,
+            Permissions: null,
+        },
+        TransferAndConnect: {
+            IsTransfer: true,
+            TransferLines: 1,
+            TransferNumber: '2142960678',
+            TransferCreditsUsed: null,
+        },
+        Audio: {
+            Uri: '/v1/audio/ah2441',
+            AudioID: 'ah2441',
+            Name: null,
+            Description: null,
+            Favorite: null,
+            Shared: null,
+            Length: 10,
+            MessageType: null,
+            ReadOnly: null,
+            Created: null,
+            LastUsed: null,
+            TextToSpeech: false,
+        },
+        AudioVM: {
+            Uri: '/v1/audio/ah2442',
+            AudioID: 'ah2442',
+            Name: null,
+            Description: null,
+            Favorite: null,
+            Shared: null,
+            Length: 13,
+            MessageType: null,
+            ReadOnly: null,
+            Created: null,
+            LastUsed: null,
+            TextToSpeech: false,
+        },
+        RetryTimes: 1,
+        CallThrottle: 0,
+        LivePersonTotal: 0,
+        AnsweringMachineTotal: 0,
+        BusyNoAnswerTotal: 0,
+        InvalidNumberTotal: 0,
+        SurveyResponseTotal: 0,
+        TransferTotal: 0,
+        SurveyResponses: null,
+        MaxMessageLength: 30,
+        MessageRecordingInstruction: null,
+        EstimatedDuration: 0,
+        EstimatedCompletion: null,
+        ExcludedDaysIgnored: false,
+        CallingWindowIgnored: false,
+        NotEnoughTimeToComplete: false,
+    },
+};
+//# sourceMappingURL=CreateCallBroadcast.mock.js.map

package/dist/extensions/text-em-all/actions/createCallBroadcast/__testdata__/CreateCallBroadcast.mock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"CreateCallBroadcast.mock.js","sourceRoot":"","sources":["../../../../../../extensions/text-em-all/actions/createCallBroadcast/__testdata__/CreateCallBroadcast.mock.ts"],"names":[],"mappings":";;;AAEa,QAAA,+BAA+B,GAAG;IAC7C,MAAM,EAAE,GAAG;IACX,UAAU,EAAE,IAAI;IAChB,OAAO,EAAE;QACP,QAAQ,EAAE,oDAAoD;KAC/D;IACD,IAAI,EAAE;QACJ,GAAG,EAAE,yBAAyB;QAC9B,mBAAmB,EAAE,iCAAiC;QACtD,WAAW,EAAE,QAAQ;QACrB,aAAa,EAAE,2CAA2C;QAC1D,aAAa,EAAE,cAAc;QAC7B,eAAe,EAAE,uBAAuB;QACxC,uBAAuB,EAAE,WAAW;QACpC,WAAW,EAAE,0BAA0B;QACvC,SAAS,EAAE,0BAA0B;QACrC,aAAa,EAAE,IAAI;QACnB,QAAQ,EAAE,YAAY;QACtB,WAAW,EAAE,IAAI;QACjB,aAAa,EAAE,CAAC;QAChB,gBAAgB,EAAE,CAAC;QACnB,cAAc,EAAE,CAAC;QACjB,IAAI,EAAE;YACJ,OAAO,EAAE,IAAI;YACb,MAAM,EAAE,MAAM;YACd,QAAQ,EAAE,IAAI;YACd,SAAS,EAAE,IAAI;YACf,QAAQ,EAAE,IAAI;YACd,KAAK,EAAE,IAAI;YACX,KAAK,EAAE,IAAI;YACX,QAAQ,EAAE,IAAI;YACd,YAAY,EAAE,KAAK;YACnB,SAAS,EAAE,IAAI;YACf,KAAK,EAAE,IAAI;YACX,WAAW,EAAE,IAAI;SAClB;QACD,kBAAkB,EAAE;YAClB,UAAU,EAAE,IAAI;YAChB,aAAa,EAAE,CAAC;YAChB,cAAc,EAAE,YAAY;YAC5B,mBAAmB,EAAE,IAAI;SAC1B;QACD,KAAK,EAAE;YACL,GAAG,EAAE,kBAAkB;YACvB,OAAO,EAAE,QAAQ;YACjB,IAAI,EAAE,IAAI;YACV,WAAW,EAAE,IAAI;YACjB,QAAQ,EAAE,IAAI;YACd,MAAM,EAAE,IAAI;YACZ,MAAM,EAAE,EAAE;YACV,WAAW,EAAE,IAAI;YACjB,QAAQ,EAAE,IAAI;YACd,OAAO,EAAE,IAAI;YACb,QAAQ,EAAE,IAAI;YACd,YAAY,EAAE,KAAK;SACpB;QACD,OAAO,EAAE;YACP,GAAG,EAAE,kBAAkB;YACvB,OAAO,EAAE,QAAQ;YACjB,IAAI,EAAE,IAAI;YACV,WAAW,EAAE,IAAI;YACjB,QAAQ,EAAE,IAAI;YACd,MAAM,EAAE,IAAI;YACZ,MAAM,EAAE,EAAE;YACV,WAAW,EAAE,IAAI;YACjB,QAAQ,EAAE,IAAI;YACd,OAAO,EAAE,IAAI;YACb,QAAQ,EAAE,IAAI;YACd,YAAY,EAAE,KAAK;SACpB;QACD,UAAU,EAAE,CAAC;QACb,YAAY,EAAE,CAAC;QACf,eAAe,EAAE,CAAC;QAClB,qBAAqB,EAAE,CAAC;QACxB,iBAAiB,EAAE,CAAC;QACpB,kBAAkB,EAAE,CAAC;QACrB,mBAAmB,EAAE,CAAC;QACtB,aAAa,EAAE,CAAC;QAChB,eAAe,EAAE,IAAI;QACrB,gBAAgB,EAAE,EAAE;QACpB,2BAA2B,EAAE,IAAI;QACjC,iBAAiB,EAAE,CAAC;QACpB,mBAAmB,EAAE,IAAI;QACzB,mBAAmB,EAAE,KAAK;QAC1B,oBAAoB,EAAE,KAAK;QAC3B,uBAAuB,EAAE,KAAK;KAC/B;CAC+B,CAAA"}

package/dist/extensions/text-em-all/actions/createCallBroadcast/config.d.ts

@@ -0,0 +1,254 @@
+import { z } from 'zod';
+import { FieldType, StringType } from '@awell-health/extensions-core';
+export declare const fields: {
+    broadcastName: {
+        id: string;
+        label: string;
+        type: FieldType.STRING;
+        required: true;
+        description: string;
+    };
+    broadcastType: {
+        id: string;
+        label: string;
+        type: FieldType.STRING;
+        required: true;
+        description: string;
+        options: {
+            dropdownOptions: {
+                label: "Announcement" | "Survey";
+                value: "Announcement" | "Survey";
+            }[];
+        };
+    };
+    startDate: {
+        id: string;
+        label: string;
+        type: FieldType.STRING;
+        required: false;
+        description: string;
+    };
+    maxMessageLength: {
+        id: string;
+        label: string;
+        type: FieldType.NUMERIC;
+        required: false;
+        description: string;
+    };
+    callerID: {
+        id: string;
+        label: string;
+        type: FieldType.STRING;
+        required: false;
+        description: string;
+    };
+    phoneNumber: {
+        id: string;
+        label: string;
+        type: FieldType.STRING;
+        stringType: StringType.PHONE;
+        required: true;
+        description: string;
+    };
+    checkCallingWindow: {
+        id: string;
+        label: string;
+        type: FieldType.BOOLEAN;
+        required: false;
+        description: string;
+    };
+    continueOnNextDay: {
+        id: string;
+        label: string;
+        type: FieldType.BOOLEAN;
+        required: false;
+        description: string;
+    };
+    transferAndConnect: {
+        id: string;
+        label: string;
+        type: FieldType.JSON;
+        required: false;
+        description: string;
+    };
+    audio: {
+        id: string;
+        label: string;
+        type: FieldType.JSON;
+        required: false;
+        description: string;
+    };
+    audioVM: {
+        id: string;
+        label: string;
+        type: FieldType.JSON;
+        required: false;
+        description: string;
+    };
+    retryTimes: {
+        id: string;
+        label: string;
+        type: FieldType.NUMERIC;
+        required: false;
+        description: string;
+    };
+    callThrottle: {
+        id: string;
+        label: string;
+        type: FieldType.NUMERIC;
+        required: false;
+        description: string;
+    };
+};
+export declare const dataPoints: {
+    broadcastId: {
+        key: string;
+        valueType: "number";
+    };
+    broadcastStatus: {
+        key: string;
+        valueType: "string";
+    };
+    uriBroadcastDetails: {
+        key: string;
+        valueType: "string";
+    };
+    broadcastStatusCategory: {
+        key: string;
+        valueType: "string";
+    };
+    broadcastStartDate: {
+        key: string;
+        valueType: "string";
+    };
+};
+export declare const FieldsSchema: z.ZodObject<{
+    broadcastName: z.ZodString;
+    broadcastType: z.ZodEnum<["Announcement", "Survey"]>;
+    startDate: z.ZodEffects<z.ZodOptional<z.ZodEffects<z.ZodDate, string, Date>>, string | undefined, Date | undefined>;
+    maxMessageLength: z.ZodOptional<z.ZodNumber>;
+    callerID: z.ZodOptional<z.ZodString>;
+    phoneNumber: z.ZodEffects<z.ZodString, string, string>;
+    checkCallingWindow: z.ZodOptional<z.ZodBoolean>;
+    continueOnNextDay: z.ZodOptional<z.ZodBoolean>;
+    transferAndConnect: z.ZodEffects<z.ZodOptional<z.ZodString>, {
+        transferNumber: string;
+        transferMessage: string;
+        transferDigit: string;
+        transferIntroduction: string;
+    } | undefined, string | undefined>;
+    audio: z.ZodEffects<z.ZodOptional<z.ZodString>, {
+        Description: string;
+        Created: string;
+        Text: string;
+        Name: string;
+        Voice: {
+            Text: string;
+            Voice: "Ivy" | "Joanna" | "Kendra" | "Kimberly" | "Salli" | "Joey" | "Justin" | "Kevin" | "Matthew";
+            TextToSpeech: boolean;
+        };
+        TextToSpeech: boolean;
+        Uri: string;
+        AudioID: string;
+        Favorite: boolean;
+        Shared: boolean;
+        Length: number;
+        MessageType: "Announcement" | "NeverUsed" | "SurveyLiveAnswer" | "SurveyVoiceMail" | "AnnouncementVoiceMail" | "TransferAndConnect";
+        ReadOnly: boolean;
+        LastUsed: string;
+    } | undefined, string | undefined>;
+    audioVM: z.ZodEffects<z.ZodOptional<z.ZodString>, {
+        Description: string;
+        Created: string;
+        Text: string;
+        Name: string;
+        Voice: {
+            Text: string;
+            Voice: "Ivy" | "Joanna" | "Kendra" | "Kimberly" | "Salli" | "Joey" | "Justin" | "Kevin" | "Matthew";
+            TextToSpeech: boolean;
+        };
+        TextToSpeech: boolean;
+        Uri: string;
+        AudioID: string;
+        Favorite: boolean;
+        Shared: boolean;
+        Length: number;
+        MessageType: "Announcement" | "NeverUsed" | "SurveyLiveAnswer" | "SurveyVoiceMail" | "AnnouncementVoiceMail" | "TransferAndConnect";
+        ReadOnly: boolean;
+        LastUsed: string;
+    } | undefined, string | undefined>;
+    retryTimes: z.ZodOptional<z.ZodNumber>;
+    callThrottle: z.ZodOptional<z.ZodNumber>;
+}, "strip", z.ZodTypeAny, {
+    phoneNumber: string;
+    broadcastName: string;
+    broadcastType: "Announcement" | "Survey";
+    startDate?: string | undefined;
+    maxMessageLength?: number | undefined;
+    callerID?: string | undefined;
+    checkCallingWindow?: boolean | undefined;
+    continueOnNextDay?: boolean | undefined;
+    transferAndConnect?: {
+        transferNumber: string;
+        transferMessage: string;
+        transferDigit: string;
+        transferIntroduction: string;
+    } | undefined;
+    audio?: {
+        Description: string;
+        Created: string;
+        Text: string;
+        Name: string;
+        Voice: {
+            Text: string;
+            Voice: "Ivy" | "Joanna" | "Kendra" | "Kimberly" | "Salli" | "Joey" | "Justin" | "Kevin" | "Matthew";
+            TextToSpeech: boolean;
+        };
+        TextToSpeech: boolean;
+        Uri: string;
+        AudioID: string;
+        Favorite: boolean;
+        Shared: boolean;
+        Length: number;
+        MessageType: "Announcement" | "NeverUsed" | "SurveyLiveAnswer" | "SurveyVoiceMail" | "AnnouncementVoiceMail" | "TransferAndConnect";
+        ReadOnly: boolean;
+        LastUsed: string;
+    } | undefined;
+    audioVM?: {
+        Description: string;
+        Created: string;
+        Text: string;
+        Name: string;
+        Voice: {
+            Text: string;
+            Voice: "Ivy" | "Joanna" | "Kendra" | "Kimberly" | "Salli" | "Joey" | "Justin" | "Kevin" | "Matthew";
+            TextToSpeech: boolean;
+        };
+        TextToSpeech: boolean;
+        Uri: string;
+        AudioID: string;
+        Favorite: boolean;
+        Shared: boolean;
+        Length: number;
+        MessageType: "Announcement" | "NeverUsed" | "SurveyLiveAnswer" | "SurveyVoiceMail" | "AnnouncementVoiceMail" | "TransferAndConnect";
+        ReadOnly: boolean;
+        LastUsed: string;
+    } | undefined;
+    retryTimes?: number | undefined;
+    callThrottle?: number | undefined;
+}, {
+    phoneNumber: string;
+    broadcastName: string;
+    broadcastType: "Announcement" | "Survey";
+    startDate?: Date | undefined;
+    maxMessageLength?: number | undefined;
+    callerID?: string | undefined;
+    checkCallingWindow?: boolean | undefined;
+    continueOnNextDay?: boolean | undefined;
+    transferAndConnect?: string | undefined;
+    audio?: string | undefined;
+    audioVM?: string | undefined;
+    retryTimes?: number | undefined;
+    callThrottle?: number | undefined;
+}>;
+export type ActionFields = z.infer<typeof FieldsSchema>;