The most common piece of feedback we received in our first few months from finance teams and ops managers with a finance remit was a short list of apps we did not yet support. Xero and QuickBooks were at the top of that list, consistently, from teams across the UK and the US. They kept coming up because they are the operational backbone for a lot of small and growing businesses — the system of record for invoices, payments, suppliers, and the financial side of order management.
We shipped those integrations this month, along with nine others that came up frequently enough to prioritise. Here is what is now available and what you can actually automate with each one.
Finance and accounting
Xero
Xero integration covers both reads and writes. You can use Xero as a trigger source (when a new invoice is created, when a payment is received, when a bill is overdue) or as a destination (create a contact record, create a draft invoice, mark an invoice as sent). The most common automation we have seen people set up immediately after connecting Xero is a payment received notification: when a Xero invoice is marked as paid, post a Slack message to the finance channel and update the relevant row in the orders tracking spreadsheet. That specific automation takes about three minutes to describe and activate.
QuickBooks Online
QuickBooks Online support covers invoice creation, customer record management, and payment status events. Teams using QuickBooks primarily for US-based billing have been asking for this since we launched. The integration supports both reading from QuickBooks (trigger on new customer, trigger on invoice status change) and writing to it (create invoice, add customer record). Worth noting: QuickBooks' sandbox environment is available for testing automations before they touch live data, which we recommend using when you are setting up financial automations for the first time.
Stripe
Stripe was already on our roadmap and several teams were waiting on it. The Stripe integration supports payment events as triggers: new payment received, subscription started, subscription cancelled, refund issued. Common use cases include logging payments to a Google Sheet, notifying a team Slack channel when a new subscription starts, and creating a customer record in your CRM when a first payment comes through. Stripe webhooks are used under the hood; Agenno handles the webhook setup so you do not need to configure it manually in your Stripe dashboard.
Operations and project management
Monday.com
Monday.com joins Asana, Trello, and Notion as a supported project management destination. You can create items, update status columns, and read from boards as trigger events. Teams that use Monday.com as their ops board of record can now describe automations that keep Monday.com in sync with other systems — for example, creating a Monday.com item when a new support ticket is opened, or updating a status column when an order ships.
Jira
Jira integration is focused on issue creation and status events. This one was requested primarily by ops teams in companies with a software product, where some operational workflows overlap with the engineering team's issue tracker — escalations that should create Jira tickets, or status updates that should flow from Jira back to an ops tracking sheet. The integration supports Jira Cloud; Jira Server support is in progress.
Pipedrive
Pipedrive CRM is now supported alongside HubSpot and Salesforce. Trigger on new deal, new contact, or deal stage change. Create and update person and deal records as outputs. For ops teams at companies where Pipedrive is the CRM, this fills the gap that previously required them to either use a different CRM for automations or do the CRM sync manually.
Communication and scheduling
Microsoft Teams
Teams messaging support has been one of the most requested integrations since we launched — unsurprisingly, given how many UK businesses operate on Microsoft 365 rather than Google Workspace. You can now send messages to Teams channels and direct messages as automation outputs. The same notification automations that work with Slack now work with Teams, using the same plain-English description format. You specify the channel name or recipient in your description; Agenno handles the rest.
Calendly
Calendly is now a trigger source: when a new booking is made, when a booking is cancelled, when a rescheduled event is confirmed. The most common automation is a post-booking CRM record creation — when someone books a demo through Calendly, create a contact record in your CRM with their name, email, and company from the booking form, and notify the relevant person via Slack or email. This replaces a manual process that typically took five to ten minutes per booking and was often skipped under time pressure.
Typeform and Tally updates
Both Typeform and Tally were already supported, but we have expanded what data is accessible from form submissions. Previously, field mapping was limited to the most common field types. This update adds support for file upload references, multi-select fields, and calculated fields, which had been a blocker for some more complex form-to-workflow automations.
What is coming next
The next integrations in the queue, based on the requests we are receiving, are FreshBooks, Zoho CRM, HubSpot Deals (we support HubSpot Contacts currently), and Intercom. We are also looking at a generic webhook receiver, which would let Agenno be triggered by any app that can send a webhook — relevant for more technically-capable users who want to connect systems we do not formally support yet.
If you are using an app that is not on the list and want to flag it, the fastest way to do that is the feedback link inside the Agenno dashboard. We track those requests directly and they feed into our integration roadmap. The finance-apps batch in this update came almost entirely from those requests.
All ten new integrations are available on all plans starting today. Existing automations are not affected. If you connect Xero or QuickBooks for the first time, you will need to go through the one-time connection flow in your integrations settings before describing automations that use them.