What we do
Tools
Industries
Department
How we workLet's talk →
Home/Actionstep/Actionstep Integrations When Zapier Runs Out
Actionstep

Actionstep Integrations, and What to Build When Zapier Runs Out

A new enquiry arrives through the website form, and someone opens Actionstep and types it in as a matter. The paralegal files the client's email from Outlook, and the accounts team waits for someone to mention the first invoice has gone out. Actionstep has more ways to connect than most firms use: its own integrations list, a Zapier app, and an API with event hooks. Which one fits depends on what has to happen, and how often.

Actionstep's Zapier app beside a build on its API

Zapier

A few matters a day, one step each

  • Triggers for a new matter, contact, task, file note or matter participant, a matter step change, and an updated matter.
  • Actions that create matters, contacts, tasks, file notes, time entries and disbursements, and read or update matter custom fields.
  • Set up and changed by someone at the firm, without a developer.
Actionstep API

Rules, volume, or a system Zapier never reaches

  • Access by scope, requested from Actionstep's Global Support Team, with a sandbox copy of your live system to test on.
  • OAuth 2 sign-in under a real Actionstep user, never the System Administrator account.
  • REST hooks for 21 events, including a matter being created, a step changing, and a time entry or disbursement being added.
  • Custom data fields, documents and file notes, paged at up to 200 records a request.

Zapier covers simple one-step hand-offs. Once a rule needs to check something first, write to several places, or run at volume, it belongs on the API.

Getting from an idea to a live Actionstep API integration

  1. 1

    Ask Actionstep for access

    Access is requested through Actionstep's Global Support Team. You describe the project so they can assign the scopes it needs, and you get an API access key and client secret. A one-time setup fee applies.

  2. 2

    Test on a copy of your own system

    Actionstep places a copy of your live system in a sandbox with an admin login, so the integration is tested on your own matter types, steps and custom fields.

  3. 3

    Sign in the way Actionstep expects

    Authentication is OAuth 2 with the authorization code flow, so every call carries one user's permissions. The token response includes an api_endpoint for your organization, and that's the base URL for every request.

    Watch for: the System Administrator login. Actionstep says not to use it for API access.

  4. 4

    Register REST hooks for the events that matter

    Register a REST hook with an event name and a target URL. Your endpoint has to answer with HTTP 200, and Actionstep disables a hook when calls to it hit an unexpected error.

    Watch for: a hook marked Disabled. A daily check of hook status belongs in the build, so a gap in events gets noticed.

  5. 5

    Pass the review and go live

    Commercial integrations go through an API review, usually a screenshare of the integration end to end. Non-commercial ones now self-certify against Actionstep's development guidelines, with at least two weeks' notice of the go-live date. Production credentials follow.

Actionstep integration questions before anything gets built

Does Actionstep have an API?

Yes. It's a REST API with OAuth 2 sign-in, access granted by scope, and REST hooks for events such as a new matter or a step change. Access is requested from Actionstep's support team, and each integration gets its own set of credentials.

What does the Actionstep Outlook plugin do?

The Outlook add-in for Office 365 files an email against the matching matter from inside Outlook, so correspondence lands in the matter without saving it and uploading it separately.

Are there prebuilt Actionstep integrations for accounting software?

Yes, for Xero. Actionstep's own Xero integration carries invoices, payments and trust transactions entered in Actionstep across to Xero, and Actionstep has accounting and trust accounting built in as well. For other accounting systems, the API's billing, time entry and disbursement data is where a custom link starts. How trust transactions should appear in the firm's books is a question for your accountant.

Which apps connect to Actionstep without a custom build?

Its integrations list includes Office 365, DocuSign, InfoTrack, First AML, Legl, bundledocs, Smith.ai and Lexidesk, among others, plus the Zapier app. Actionstep notes that it doesn't vouch for third-party integrations, so test each one against how your firm works.

Who builds an Actionstep integration on the API?

n-frames builds them for firms on Actionstep: web and phone enquiries opened as matters with their contacts, step changes that start work in other systems, and time entries and disbursements carried to tools Actionstep has no connector for. Each one gets its own Actionstep user and listens on REST hooks where an event exists.

Actionstep integrations that stop without anyone noticing

Built on one person's login

How you'll know: All API activity runs as a user. When that person leaves and their account is closed, the integration stops with them.

Fix: Give the integration its own Actionstep user with only the permissions it needs, and record who owns it.

A hard-coded API address

How you'll know: Requests point at a fixed URL instead of the api_endpoint returned with the token.

Fix: Read the base URL from each token response. Actionstep's review checks for it.

No plan for throttling

How you'll know: A bulk update fails partway through with HTTP 429.

Fix: Retry with backoff, and page through results instead of asking for everything at once.

Looking for "matters" in the API docs

How you'll know: A developer searches the endpoint list for matters and finds actions instead.

Fix: In Actionstep's API a matter is an action, so ActionCreated is the hook that fires for a new matter.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.