Connect ChargeOver to Payaca

Both apps 35ChargeOver 21Payaca 14

• Trigger
  Contact Was Updated

  Triggers when a contact is updated in ChargeOver.

• Action
  Add item

  Create an item (product or discount).

• Action
  Add note

  Add a note to a customer, invoice, etc.

• Action
  Add Transaction

  records a payment, refund or credit against a customer (e.g. transaction_type=pay, gateway_method=check, amount) without charging a payment gateway. Creates a transaction record.

• Action
  Cancel a Subscription

  Cancel an existing subscription in ChargeOver.

• Action
  Create a Contact

  Create a new contact in ChargeOver.

• Action
  Create a Customer

  Create a new customer in ChargeOver.

• Action
  Create an Invoice

  Create a new Invoice in ChargeOver.

• Action
  Create a Subscription

  Create a new subscription in ChargeOver.

• Action
  Delete Item

  deletes an item (product/discount) by id.

• Action
  Find Contact

  Finds an existing contact by a specified field.

• Action
  Find Customer

  Finds an existing customer by a specified field.

• Action
  Find Item (Product, Discount)

  Finds an existing item (product, discount) by a specified field.

• Action
  Find Subscription

  Finds an existing subscription by a specified field.

• Action
  List Notes

  Lists the notes attached to a ChargeOver record (customer, invoice, subscription, contact), filtered by record type and record ID.

• Action
  Update a Customer

  Update a existing customer in ChargeOver.

• Action
  Update contact

  Update a user/contact.

• Action
  Update invoice

  Update an invoice.

• Action
  Update item

  Update an item.

• Action
  Update subscription

  Update a subscription (package).

• Action
  Void Transaction

  marks an existing transaction voided in ChargeOver (logs an externally-voided transaction; does not contact the gateway), changing its status.

• Action
  Add invoice

  Creates an invoice against a Payaca project for a fixed amount, a percentage of the accepted project value, or everything still payable, and can optionally send it or mark it as sent.

• Action
  Add payment

  Records a payment against a Payaca project, optionally reconciling it to a specific invoice and emailing the customer a receipt. Returns the created payment and how it was reconciled.

• Action
  Add project note

  Adds one or more notes to a Payaca project and returns the notes that were created.

• Action
  Add proposal

  Creates a proposal on a Payaca project, with its line items, optional payment schedule and any grants. Returns the new proposal with its totals.

• Action
  Get customer

  Returns a customer by id, including their contacts, addresses, custom field values and tags.

• Action
  Get invoice

  Returns a Payaca invoice by its ID, including its status, totals, line items and linked project. An error occurs if the invoice is not found.

• Action
  Get project

  Returns a project by its id, including its customer, pipeline stage, site address, custom fields, totals, grants and expected payments.

• Action
  Get scheduled event

  Returns a single scheduled event, including its times, location, customer, project, assignees, notes, tags and contacts to notify. An error occurs if the event is not found.

• Action
  List customers

  Returns all customers in the Payaca account, optionally narrowed to those with a contact on a given email address or phone number.

• Action
  List pipelines

  Returns all pipelines in the Payaca account, including each pipeline's stages in order.

• Action
  List projects

  Returns the projects in the Payaca account, optionally only those belonging to one customer.

• Action
  Mark proposal as accepted

  Marks a proposal that was already sent to the customer as accepted and returns the updated proposal.

• Action
  Update project

  Updates the custom field values on an existing project and returns the updated project. Service-type projects cannot be updated.

• Action
  Update scheduled event

  Updates the name, description, start time or end time of an existing scheduled event, and returns the updated event.

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