Connect Frihet and ilert

Both apps 51Frihet 38ilert 13

• Trigger
  New Expense

  Fires when a new expense is created. Backed by vendor webhook registration.

• Action
  Add Client

  Create a client.

• Action
  Add Deposit

  Create a deposit.

• Action
  Add Expense

  Create an expense.

• Action
  Add Invoice

  Create an invoice.

• Action
  Add Product

  Create a product.

• Action
  Add Quote

  Create a quote.

• Action
  Add Vendor

  Create a vendor.

• Action
  Apply deposit to invoice

  Apply a deposit balance to an invoice.

• Action
  Delete Client

  Delete a client.

• Action
  Delete Expense

  Delete an expense.

• Action
  Delete Invoice

  Delete an invoice.

• Action
  Delete Product

  Delete a product.

• Action
  Delete Quote

  Delete a quote.

• Action
  Delete Vendor

  Delete a vendor.

• Action
  Get Client

  Retrieve a client by id.

• Action
  Get Deposit

  Retrieve a deposit by id.

• Action
  Get Expense

  Retrieve an expense by id.

• Action
  Get Invoice

  Retrieve an invoice by id.

• Action
  Get Product

  Retrieve a product by id.

• Action
  Get Quote

  Retrieve a quote by id.

• Action
  Get Vendor

  Retrieve a vendor by id.

• Action
  List Clients

  List clients.

• Action
  List Deposits

  List deposits.

• Action
  List Expenses

  List expenses.

• Action
  List Invoices

  List invoices.

• Action
  List Products

  List products.

• Action
  List Quotes

  List quotes.

• Action
  List Vendors

  List vendors.

• Action
  Mark invoice as paid

  Mark an invoice as paid.

• Action
  Send Invoice

  Send invoice by email to the client.

• Action
  Send Quote

  Send quote by email to the client.

• Action
  Update Client

  Partial update a client.

• Action
  Update Expense

  Partial update an expense.

• Action
  Update Invoice

  Partial update an invoice.

• Action
  Update Product

  Partial update a product.

• Action
  Update Quote

  Partial update a quote.

• Action
  Update Vendor

  Partial update a vendor.

• Trigger
  New or Updated Incident

  Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed.

• Action
  Accept Incident

  Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.

• Action
  Add Alert

  Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify).

• Action
  Add maintenance window

  Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.

• Action
  Create Incident

  Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.

• Action
  Find User on Call

  Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call.

• Action
  Get alert

  Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.

• Action
  Get incident

  Returns a single ilert incident by its id, including its status, severity, affected services and responders.

• Action
  Get maintenance window

  Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.

• Action
  List Alert Sources

  Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.

• Action
  List incidents

  Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.

• Action
  List users

  Returns the users in your ilert account, with their name, email, role and contact settings.

• Action
  Resolve Incident

  Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.

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