Skip to main content
Let’s learn how to connect Engini to Expensify. This integration lets you manage Expensify policies, expense reports, expenses, employees and expense rules directly from your Engini workflows. To get started, create an account at Expensify.

Add a Connection to Expensify in Engini

Prerequisites

  • An Expensify account.
  • A Partner User Id and a Partner User Secret from Expensify.
  • For the Get Domain Credit Cards action only: an Expensify domain admin account.

Retrieve your Expensify credentials

  1. Sign in to Expensify and make sure your Expensify account is validated.
  2. Open https://www.expensify.com/tools/integrations/.
  3. Click Generate API credentials. Expensify shows your Partner User Id and your Partner User Secret.
  4. Copy both values.
Note: Expensify shows the Partner User Secret only once. Save it before you leave the page; if you lose it, generate new credentials.

Connecting Engini to Expensify

  1. Enter your Engini account at https://app.engini.io.
  2. Navigate to the Connections page by clicking on Connections in the left sidebar or by clicking here. Engini - Connections page
  3. Click on the “New Integration” option located at the top bar. Engini - New Integration button
  4. Choose the Expensify option from the available applications. Expensify - Choose Application
  5. Enter the following details in the “New Integration” form and press Save: Expensify - New Integration form 1. Connection Name - Enter a name that helps identify the Expensify connection, for example “Expensify - Finance team”. 2. Partner User Id - Enter the Partner User Id that Expensify generated for you on the Integrations page. 3. Partner User Secret - Enter the Partner User Secret that Expensify generated for you. It is the value Expensify shows only once. 4. Employee Email - Optional. Enter the email address of the Expensify employee that your actions should work with by default. Actions that have an Employee Email field use this address when you leave that field empty. 5. Save - Click Save to create the connection.

Actions

The actions below work on Expensify policies, expense reports, expenses, employees and expense rules. Wherever an action asks for a Policy Id, click the empty field to open the tooltip and choose one of the policies of your Expensify account, or map the Id from a previous step such as Get Policies.

Create Expense

Creates a new expense for an employee in Expensify. Expensify - Create Expense action
  1. Employee Email - The email address of the employee the expense is created for. If you leave it empty, Engini uses the Employee Email from your connection.
  2. Merchant - The name of the merchant of the expense, for example “Office Depot”.
  3. Amount - The amount of the expense, in cents. For example, enter 2500 for 25.00.
  4. Currency - The three-letter code of the currency of the expense, for example USD.
  5. Created Date - The date of the expense, in the format yyyy-MM-dd, for example 2026-10-31.
  6. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.
All of the following are optional and are added through Add Field:
  • External Id - Your own identifier for the expense, if you keep one outside Expensify.
  • Category - The Expensify category of the expense.
  • Tag - The Expensify tag of the expense.
  • Billable - Whether the expense is billable.
  • Reimbursable - Whether the expense is reimbursable.
  • Comment - A comment to store on the expense.
  • Report Id - The Id of an existing report to add the expense to.
  • Tax: Rate Id - The Id of the tax rate of the expense.
  • Tax: Amount - The tax amount of the expense.
  • Policy Id - The policy the expense belongs to. Click the empty field to open the tooltip and choose a policy.

Create Expense Report

Creates a new expense report in Expensify and adds expenses to it. Expensify - Create Expense Report action
  1. Employee Email - The email address of the employee the report is created for. If you leave it empty, Engini uses the Employee Email from your connection.
  2. Policy Id - The policy the report belongs to. Click the empty field to open the tooltip and choose a policy, or map it from a previous step such as Get Policies.
  3. Report Title - The title of the new report, for example “October trip”.
  4. Expenses - The expenses to add to the report, mapped from an earlier step in your workflow. Each expense has a date, a currency, a merchant and an amount in cents.
The step returns the Id and the name of the new report. Note: Expensify can report a problem inside a reply that Engini shows as successful. In a later step, check the response code field that Expensify returns. Any value other than 200 means Expensify did not create the report.

Create Policy

Creates a new policy in Expensify. Expensify - Create Policy action
  1. Policy Name - The name of the new policy, for example “Sales Team”.
  2. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.
All of the following are optional and are added through Add Field:
  • Plan - The Expensify plan of the new policy.

Create Policy Expense Rule

Creates an expense rule in an Expensify policy. Expensify - Create Policy Expense Rule action
  1. Employee Email - The email address of the employee the rule is created for. If you leave it empty, Engini uses the Employee Email from your connection.
  2. Policy Id - The policy the rule belongs to. Click the empty field to open the tooltip and choose a policy, or map it from a previous step such as Get Policies.
  3. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.
All of the following are optional and are added through Add Field:
  • Tag - The tag the rule applies to expenses.
  • Default Billable - Whether expenses that match the rule are billable by default.

Create Report Template

Creates a report template that you can use to export reports with the Export Report action. Expensify - Create Report Template action
  1. Template Format - The file format of the exported report. Click the empty field to open the tooltip and choose a format.
  2. Name - The name of the template. It starts as “Report Template” and you can rename it to fit your use case.

Export Report

Exports reports from Expensify with a report template that you created earlier in the workflow. For more about exporting reports, see the Expensify report exporter. Expensify - Export Report action
  1. Report Template - Choose the report template created by a previous Create Report Template step.
  2. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.
All of the following are optional and are added through Add Field:
  • Input: Report State - Which reports Expensify exports, by their state.
  • Input: Limit - The maximum number of reports to export.
  • Input: Employee Email - Export only the reports of this employee.
  • Filter: Report Ids - Export only the reports with these Ids.
  • Filter: Policy Ids - Export only the reports of these policies. Click the empty field to open the tooltip and choose them.
  • Filter: Start Date and Filter: End Date - Export only the reports in this period. Use the format yyyy-MM-dd.
  • Filter: Approved After - Export only the reports approved after this date, in the format yyyy-MM-dd.
  • Filter: Marked As Exported - Filter the reports by the export mark they already have.
  • Output: File Basename - The name of the exported file.
  • Output: Include Full Page Receipts Pdf - Whether the export includes a PDF with the full-page receipts.
  • On Finish: Mark As Exported - The export mark Expensify sets on the reports when the export is done.
  • On Finish: Email Recipients and On Finish: Email Message - Who Expensify emails when the export is done, and the message it sends.

Get Domain Credit Cards

Retrieves the company credit cards of an Expensify domain. Expensify - Get Domain Credit Cards action
  • Domain - The Expensify domain whose cards you want to retrieve, for example company.com.
Each card is returned with details such as its Id, name, bank and the email of the cardholder. Note: This action works only with the credentials of an Expensify domain admin. With any other account, Expensify refuses the request. Note: Expensify can report a problem inside a reply that Engini shows as successful. In a later step, check the response code field that Expensify returns. Any value other than 200 means Expensify did not return the cards.

Get Policies

Retrieves the policies of your Expensify account. Expensify - Get Policies action
  • Add Filter - Click Add Filter to define conditions that narrow down the data list and return only the relevant items. To learn more about using filters, click here.

Get Policy

Retrieves an existing policy. Expensify - Get Policy action
  1. Policy Id - The policy you want to retrieve. Click the empty field to open the tooltip and choose a policy, or map it from a previous step such as Get Policies.
  2. Fields - The parts of the policy you want to retrieve, as an array. Click the empty field to open the tooltip and use the CreateArray function, then add each field you need to the array.
  3. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.
All of the following are optional and are added through Add Field:
  • User Email - The email address of the user whose view of the policy you want to retrieve.

Update Employee

Updates an existing employee in Expensify. Expensify - Update Employee action
  1. Employee Email - The email address of the employee to update. If you leave it empty, Engini uses the Employee Email from your connection.
  2. Manager Email - The email address of the employee’s manager.
  3. Employee Id - The external identifier of the employee in your own systems.
  4. Policy Id - The policy of the employee. Click the empty field to open the tooltip and choose a policy, or map it from a previous step such as Get Policies.
  5. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.
All of the following are optional and are added through Add Field:
  • First Name - The first name of the employee.
  • Last Name - The last name of the employee.
  • Custom Field 1 and Custom Field 2 - Custom values stored on the employee.
  • Approval Limit - The approval limit of the employee.
  • Limit Approver and Over Limit Approver - Who approves the reports of the employee, within and above the approval limit.
  • Approves To - The email address of the person the employee’s reports go to for approval.
  • Role - The role of the employee.
  • Domain Group Id - The domain group of the employee.
  • Is Terminated - Whether the employee has left the company.
  • Set Employee Primary Policy - The primary policy of the employee.
  • Additional Policy Ids - Other policies of the employee. Click the empty field to open the tooltip and choose them.
  • Should Fix Approval Chains - Whether Expensify repairs the approval chains after the update.
  • Dry-run - Check the update without applying it.
  • On Finish: Email Recipients - Who Expensify emails when the update is done.

Update Expense Rules

Updates an existing expense rule of a policy. Expensify - Update Expense Rules action
  1. Employee Email - The email address of the employee that owns the rule. If you leave it empty, Engini uses the Employee Email from your connection.
  2. Policy Id - The policy the rule belongs to. Click the empty field to open the tooltip and choose a policy, or map it from a previous step such as Get Policies.
  3. Rule Id - The Id of the rule you want to update.
  4. Tag - Optional. The new tag of the rule, for example “Travel”.
  5. Default Billable - Optional. Click the empty field to open the tooltip and choose Yes or No to set whether expenses that match the rule are billable by default.
Note: Expensify can report a problem inside a reply that Engini shows as successful. In a later step, check the response code field that Expensify returns. Any value other than 200 means Expensify did not update the rule.

Update Policy

Updates an existing policy in Expensify. Expensify - Update Policy action
  1. Policy Id - The policy you want to update. Click the empty field to open the tooltip and choose a policy, or map it from a previous step such as Get Policies.
  2. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.
All of the following are optional and are added through Add Field:
  • Tag Level - The tag levels of the policy.
  • Categories - The categories of the policy.
  • Report Fields - The report fields of the policy.

Update Report Status

Marks expense reports as reimbursed in Expensify. Expensify - Update Report Status action
  1. Report Ids - Optional. The Ids of the reports to mark as reimbursed, separated by commas, for example R001,R002.
  2. Start Date - Optional. Use a start date and an end date instead of report Ids to mark all the reports of that period. The field is needed when you don’t enter report Ids. Use the format yyyy-MM-dd.
  3. End Date - Optional. The last date of the period, in the format yyyy-MM-dd, for example 2026-10-31.
  4. Payment Source - Optional. The payment source to record for the reimbursement, for example ADP.
The step returns the Ids of the reports it updated, the reports it skipped and the reports that failed. Reports that can’t be marked as reimbursed, for example reports that are still Open, are returned as skipped. Note: Expensify can report a problem inside a reply that Engini shows as successful. In a later step, check the response code field that Expensify returns. Any value other than 200 means Expensify did not update the reports.

Initialize Objects Array

Creates and sets up an array, a structured collection of objects, that you can use throughout your workflow. Expensify - Initialize Objects Array action
  1. Name - The name of the array. It starts as “object array” and you can rename it to fit your use case. You will use this name whenever you refer to the array later in the workflow.
  2. Object Item Type - Select the type of object the array will store. The type you choose opens its fields so you can fill in the values of the first entry.
The object types are:
  • Category - A classification of the type of expense, for example office supplies. Read more.
  • Report Field - Data that specifies details in a report, for example information about a relocation. Read more.
  • Tag - A component that lets you assign an expense to a department, location or project.
  • Tag Level - One or more tags, each potentially containing sub-tags within a parent tag. Read more.

Append Item To Array

Adds an item to an existing array variable in your workflow. Expensify - Append Item To Array action
  1. Variable - Select the array variable you want to add an item to. This must be an array you already created with Initialize Objects Array.
  2. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.

Map Object Type Array

Transforms a list of data into an array with a different structure. Expensify - Map Object Type Array action
  1. Data List - Choose a list of data that you got from a previous step in your workflow. It holds the array of objects you want to process and transform.
  2. Object Element Type - Select the type of object each item is turned into: Category, Report Field, Tag or Tag Level. The type you choose defines the fields you fill in next.
  3. Add Field - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, click here.

Send API Request

This activity allows you to send a custom API request directly to Expensify’s API. Expensify - Send API Request action
  1. Base Url - The root URL of the Expensify API. It is filled in from your Expensify connection and can’t be edited here.
  2. Relative url - You can specify additional path segments or parameters that need to be added to the end of the Base Url. This allows you to customize the specific request you want to perform.
  3. Method - Select the HTTP method (e.g., Get, Post, Put, Delete, Patch). The default is POST.
  4. Body Type - Defines the format of the data in the body of your request. The default, application/json, means the body contains a JSON-formatted payload.
    • application/json – Sends the request body in JSON format. Commonly used by REST APIs.
    • custom – Allows you to define a custom body format by manually setting the Content-Type header. Add a Content-Type row in Add Headers with the media type you need (for example application/xml). With any other Body Type, a Content-Type you type in Add Headers is not sent; Engini sets it from the Body Type, and the run history shows it under headersnotsent.
    • application/x-www-form-urlencoded – Sends the body as URL-encoded key-value pairs, commonly used in form submissions.
    • file – Sends a file as the request body.
    • multipart/form-data – Sends form data that may include both text fields and files.
    • text/html – Sends the request body as HTML content.
    • text/plain – Sends the request body as plain text.
    • text/xml – Sends the request body in XML format.
  5. Body - Contains any data that is being sent to the server.
  6. Add Headers - Additional metadata about the request, such as the type of data Engini can accept, the length of the request body, and authentication information.
  7. Add Queries - The query refers to the parameters or data that are included in the URL of an HTTP request to provide additional information or instructions to the server.
For the full list of endpoints, see the Expensify Integration Server reference.