Connect TextIt to Spike.sh

Both apps 39TextIt 14Spike.sh 25

• Trigger
  New contact

  Triggers when a new contact is added to your TextIt workspace, optionally only contacts in a chosen group.

• Trigger
  New message

  Triggers when a new message is sent or received in your TextIt workspace, optionally limited to a folder or label.

• Action
  Add broadcast

  Creates and sends a new message broadcast to contacts, phone numbers/URNs or contact groups.

• Action
  Add contact

  Creates a new contact in your TextIt workspace with a name, language, URNs (phone, email, etc.), groups and contact field values.

• Action
  Add contact field

  Creates a new custom contact field in your TextIt workspace.

• Action
  Add group

  Creates a new contact group in your TextIt workspace.

• Action
  Delete contact

  Deletes a contact, identified by its UUID or one of its URNs.

• Action
  Find contacts

  Finds contacts by UUID, URN, group or modification date and returns the matching contacts.

• Action
  Find messages

  Returns messages in your TextIt workspace, filtered by message, folder, label or creation date, most recent first.

• Action
  List broadcasts

  Returns the broadcasts sent from your TextIt workspace, most recent first, optionally filtered by broadcast id or creation date.

• Action
  List contact fields

  Returns the custom contact fields defined in your TextIt workspace, with each field's key, name and data type.

• Action
  Perform contact action

  Performs a bulk action on up to 100 contacts: add to or remove from a group, block, unblock, interrupt active flow runs, or permanently delete.

• Action
  Start Flow

  Starts contacts, groups or URNs down a TextIt flow and returns the created flow start.

• Action
  Update contact

  Updates an existing TextIt contact, identified by its UUID or one of its URNs. Only the values you fill in are changed.

• Action
  Acknowledge incident

  Acknowledge one or more Spike.sh incidents by counter id or incident id.

• Action
  Add alert rule

  Create a new alert routing/automation rule with conditions and actions.

• Action
  Add escalation

  Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.

• Action
  Add integration

  Create a new integration for a team (source system that sends alerts into Spike).

• Action
  Add on-call

  Create a new on-call schedule for a team.

• Action
  Add service

  Create a new service in a team, with name and description.

• Action
  Create Incident

  Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.

• Action
  Delete alert rule

  Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.

• Action
  Delete escalation

  Archives (soft-deletes) a Spike escalation policy by its ID.

• Action
  Escalate incident

  Escalates one or more Spike incidents to the next step of their escalation policy.

• Action
  Get escalation

  Get escalation policy details by id.

• Action
  Get incident

  Fetch a single incident by counter id.

• Action
  Get integration

  Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.

• Action
  Get service

  Get a Spike service's details, along with its incidents and open-incident count.

• Action
  List alert rules

  Lists all alert rules (enabled and disabled) configured for a Spike team.

• Action
  List escalations

  Lists the escalation policies that belong to a Spike team.

• Action
  List incidents

  Lists the incidents for a Spike.sh team.

• Action
  List on-calls

  Lists the on-call schedules for a team.

• Action
  List services

  Lists the services in a Spike team.

• Action
  List teams

  Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.

• Action
  Resolve incident

  Resolve one or more incidents by counter id array.

• Action
  Update alert rule

  Replace an existing Spike alert rule's name, conditions and actions.

• Action
  Update escalation

  Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.

• Action
  Update on-call

  Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.

• Action
  Update service

  Updates the name and/or description of an existing Spike.sh service.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.