Connect MailerLite to Spike.sh

Both apps 44MailerLite 19Spike.sh 25

• Trigger
  Campaign Sent

  Triggers when a campaign has been sent out.

• Trigger
  Spam Complaint

  Triggers when a subscriber issues a spam complaint about an email.

• Trigger
  Subscriber Added to Group

  Triggers when a subscriber is added to a group.

• Trigger
  Subscriber Bounced

  Triggers when an email to a subscriber bounces.

• Trigger
  Subscriber Completed Automation

  Triggers when a subscriber completed a selected workflow.

• Trigger
  Subscriber Created

  Triggers when a subscriber was created on your mailing list.

• Trigger
  Subscriber Fields Updated

  Triggers when the subscriber fields have been updated.

• Trigger
  Subscriber Removed From Group

  Triggers when a subscriber has been removed from a group.

• Trigger
  Subscriber Triggered Automation

  Triggers when a subscriber triggers a selected workflow.

• Trigger
  Subscriber Unsubscribed

  Triggers when a subscriber has unsubscribed from your mailing list.

• Action
  Add Subscriber to a Group

  Add existing subscriber to a specific group by email address.

• Action
  Change Subscriber Email

  Change subscriber email to another.

• Action
  Create a Draft Campaign

  Create a Draft Campaign

• Action
  Create or Update Subscriber

  Create a new subscriber or Update an existing subscriber based on their email.

• Action
  Create Subscribers Group

  Create a new subscribers group.

• Action
  Find a Group

  Search for a group by name

• Action
  Find a Subscriber

  Search for a subscriber by email or name

• Action
  Remove Subscriber From a Group

  Remove subscriber from a specific group by email address.

• Action
  Unsubscribe Subscriber

  Sets the contact's status to "Unsubscribed".

• 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.