Connectors
The ERP, the portals and the inbox, together.
- The ERP on your own server, read-only.
- Portals and apps with an API, built from their docs.
- Partners' files by email, SFTP or FTP.
One view across the ERP, the fulfillment portal and the email thread, refreshed on a schedule.
Invoices, purchase orders and forms read to a schema and landed as rows, with a cost estimate before it runs.
A threshold watched, and the alert sent with the record attached.
One workflow writes it to the app with an API and prepares an import file for the ERP, with a person approving before anything posts.
Parties, dates, amounts and obligations extracted from the agreement, so you can ask about them.
An agent reads the week across systems and writes the update for a person to send.
Connectors
Context layer
Workflows, Alerts & Surfaces
Ask where an order is, and the ERP, the portal and the email thread answer as one record, with any guessed link put to you to confirm.
Sales and customer service ask the ERP read-only from their own AI, so the order question stops coming to you.
Describe an order board and publish it as a Surface on data kept current, so the shipping floor and the customer team work from one list.
A new connection says what it couldn't reach, so a gap in the portal doesn't quietly drop orders from the view.
Ship dates read from every order confirmation land in a table, so the late supplier shows up before the customer calls.
Connect the ERP read-only and ask where it is.
Security
Prepare the September close.
September close
Prepared · waiting for your approval
Bank reconciliation
412 of 415 lines matched
The close, prepared for approval
Why did we miss the month?
September revenue
$412,000 of $460,000
Pipeline
HubSpot · 2 deals moved to October
One answer across the business
Brief me on Northwind.
Account brief · Northwind
Ready before the 2pm call
Zendesk · tickets
Northwind · last 30 days
An account brief before every call
Yes, for everything altspark does. Every workflow run records each step with its settings, output and logs, timestamped and searchable, and every MCP tool call is logged with who made it. Changes made in your other systems stay in those systems' own audit trails, and altspark can sync that history in when the system exposes it.
Often, yes. If its data sits in SQL Server, PostgreSQL, MySQL or an ODBC source, as with Sage 100, altspark reads it through altbot. If the ERP can export files or email reports, altspark can take those in too.
Yes, in three ways. Give a workflow its own email address, and each message starts it with its attachments; add conditions, such as the sender or subject, so only the messages you want start it. Publish a Surface where partners upload files themselves, limited to the partners you let in. Or have a partner's system send files to a workflow's webhook.
Book a demo and bring the order you chased last week.