--- title: "Amwork Integration" description: "Amwork is a modular business workspace that combines CRM, boards, tasks, documents, and email in one account. Agents create and update CRM entities with custom fields, move records through board stages, assign tasks with subtasks and comments, and read the reporting dashboards." url: https://flowrunner.ai/integrations/amwork date_modified: 2026-09-04T19:38:13-07:00 --- # Amwork [CRM](https://flowrunner.ai/integrations/category/crm-sales) Amwork is a modular business workspace that combines CRM, boards, tasks, documents, and email in one account. Agents create and update CRM entities with custom fields, move records through board stages, assign tasks with subtasks and comments, and read the reporting dashboards. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 114 actions · API key · available [Amwork website](https://amwork.com/) · [Platform Documentation](https://amwork.com/) · Capability data verified 2026-08-24 1. An inbound email arrives in a connected workspace mailbox from an unknown sender 2. Get Mail Message returns the body, headers and attachment list 3. Search Entities looks for an existing record on the email address across every entity type 4. Create Contact From Mail turns the unknown sender into a CRM record 5. Create Task assigns follow-up, and Add Note attaches the message context to the record 6. The owner sees it on their board, and Get Unseen Notification Count confirms it landed 7. The owner decides whether this belongs in the pipeline or is a supplier that needs no deal ## What This Integration Enables Amwork is a single workspace that carries CRM records, boards, tasks, activities, email, documents and files, and it takes one position that decides how every workflow against it has to be written: the CRM is schemaless by design. There is no universal name field and no universal email field. There is an entity type this workspace happened to define, with field ids this workspace happened to assign. That is a real advantage for teams whose process does not fit a vendor's idea of a deal, and it means an agent has to discover the shape before it writes. FlowRunner agents do exactly that. They read List Entity Types and Get Field Settings to learn the model, then write through it: Set Entity Field Value touches one field by id without needing to understand the rest of the record, Update Entity patches only the keys sent, and Search Entities finds a person across every type when the flow does not know where they live. Around the records, agents move cards through board stages, open and comment on tasks, log activities, render an email template against a record and read what the recipient would see before anything sends. The [connectors](https://flowrunner.ai/concepts/connectors) do the discovery and the mechanical writing; the calls that reshape the workspace itself are held for a person. ### Without FlowRunner **Schema known by memory**: Only the person who built the workspace knows which field id holds the email address **Records touched wholesale**: An update to one value rewrites a record because that is the only tool available **Email and CRM apart**: The message that started the relationship lives in a mailbox the record cannot see ### With FlowRunner **Schema read before writing**: The flow discovers the entity types and field ids it needs before it touches a record **Records touched precisely**: A single field is written by id, leaving everything the flow does not understand alone **Email inside the record**: Inbound mail becomes a contact, a note and a task without anybody retyping an address ## Use Case Scenarios ### Inbound mail becomes a tracked relationship A message lands in a connected mailbox. The agent reads it with Get Mail Message, downloads anything attached with Download Mail Attachment, and calls Search Entities on the sender's address rather than assuming which entity type a contact should live in. If nothing matches, Create Contact From Mail turns the sender into a record in one call instead of copying an address by hand. The agent then adds a note, attaches the downloaded file with Upload File and Add Entity Files, and opens a follow-up with Create Task. The reply itself waits, because Send Mail goes out from the workspace's own address. ### Pipeline hygiene that runs itself On a schedule, the agent calls List Board Cards for the sales board and Get Entity Feed for records that have not moved. Deals with no activity for a set period get an activity logged with Create Activity and a task raised for their owner. Deals whose upstream signal changed, perhaps a payment recorded in [Stripe](https://flowrunner.ai/integrations/stripe) or an order in [Shopify](https://flowrunner.ai/integrations/shopify), get moved by writing the stage field with Set Entity Field Value. A summary from Get Pipeline Report and Get Top Sellers posts into [Slack](https://flowrunner.ai/integrations/slack) on Monday morning, built from live records rather than an export. ### Quoting and document generation from the record When a deal reaches the stage that needs paperwork, the agent calls List Document Templates, generates the document with Create Document against the record, and lists what it produced with List Entity Documents. Before any covering email goes out, Process Email Template renders the template against the same record so the flow can see the resolved merge fields rather than trusting them. The rendered preview goes to the deal owner. The send is theirs. ## Human-in-Loop Highlight The operation that stops this agent is not a record write. It is Update Entity Type Fields, and the reason is peculiar to a schemaless workspace. That call is a full replacement of an entity type's field definitions, so any field left out of the array is removed, and the data stored in that field goes with it, across every record of that type. Nothing in the response tells you how much disappeared. Worse, because the field ids carry names this workspace invented, an agent cannot tell from a field called `status_2` whether it is dead scaffolding or the column the operations team sorts on every day. So when a schema change is requested, the agent reads Get Field Settings, computes the exact difference between the current definitions and the proposed ones, counts the affected records with List Entities, and posts the result: "This change removes three fields from the Deal type. Two are empty. The third holds a value on four hundred and six records. Applying this deletes those values. Proceed?" A person answers. The same gate covers Delete Entity Type, which takes every record of that type with it, and Batch Delete Entities, where a filter that matches more than intended deletes more than intended. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 114 actions ### Entity Types and Fields 9 - **List Entity Types** Returns the record types this workspace defines. The starting point for any flow, because an entity type is whatever the workspace called it and its id is what everything else takes. - **Get Entity Type** Returns one entity type with its configuration. - **Create Entity Type** Defines a new record type in the workspace. Amwork publishes no fixed field list, so the definition travels as a properties object. - **Update Entity Type** Changes an entity type. A full replacement, so the type is read first and sent back with the changes applied. - **Update Entity Type Fields** Replaces an entity type's field definitions. Any field left out is removed, and the data in that field goes with it. This is the operation this page's human gate is built on. - **Delete Entity Type** Deletes an entity type. Every record of that type goes with it. - **Get Field Settings** Returns an entity type's field settings. This is where a flow discovers the field ids that Set Entity Field Value takes. - **Update Field Settings** Changes one field's settings on an entity type. - **Check Field Formula** Validates a formula field's expression before it is saved. ### Records 21 - **List Entities** Returns the records of one entity type. The filter, sort and paging travel in the request body rather than the query string. - **Get Entity List Item** Returns one record in the shape the list view uses, with its field values resolved for display. - **Get Entity List Meta** Returns the columns and totals a record list renders around its rows. - **Get Entity** Returns one record with its raw field values. - **Get Entity Info** Returns a record's summary card: who owns it, which board and stage it sits on, and its headline values. - **Create Entity** Creates a record. Field values are a pass through object keyed by field id, which Get Field Settings names. - **Update Entity** Changes a record, touching only the keys sent. - **Set Entity Field Value** Writes one field on a record by id. The safest write in the connector, because a flow can change a single value without understanding the rest of the record. - **Delete Entity** Deletes a record. - **Batch Update Entities** Changes many records of one type at once. - **Batch Delete Entities** Deletes many records of one type at once. The body selects what goes, so a filter matching more than intended deletes more than intended. - **Search Entities** Searches records across the workspace rather than within one entity type, which is how a flow finds a contact by phone or email without knowing where the record lives. - **Find Entity For Call** Finds the single record matching an inbound call. Amwork's own telephony screen pop uses this, so it is the right lookup for a phone number. - **Import Entities** Imports records into an entity type in bulk, using the layout Get Import Template returns. - **Get Import Template** Returns the import file layout for an entity type and stores it in FlowRunner file storage. - **Get Entity Feed** Returns a record's activity feed: what changed, who changed it and when. - **List Entity Files** Returns the files attached to a record. - **Add Entity Files** Attaches already uploaded files to a record by file id. Upload File is what turns bytes into one. - **Add Note** Adds a note to a record. - **Update Note** Changes a note. A full replacement, so the whole note is sent. - **Delete Note** Deletes a note from a record. ### Boards and Stages 12 - **List Boards** Returns the workspace's boards. A board is a pipeline and its stages are the columns records move through. - **Get Board** Returns one board. - **Create Board** Creates a board for an entity type. - **Update Board** Changes a board. - **Delete Board** Deletes a board. Its stages go too, and the records themselves survive. - **List Stages** Returns a board's stages. - **Get Stage** Returns one stage of a board. - **Create Stage** Adds a stage to a board. - **Update Stage** Changes a stage. - **Delete Stage** Removes a stage from a board. Records sitting in it have to go somewhere, so the board is checked before a stage holding cards is removed. - **List Board Cards** Returns the records on a board grouped by stage, with the filter traveling in the request body. - **Get Board Card** Returns one record in its board card shape. ### Tasks 15 - **Get Task** Returns one task. - **Create Task** Creates a task. - **Update Task** Changes a task, touching only the keys sent. - **Delete Task** Deletes a task. Its subtasks and comments go with it. - **List Task Cards** Returns tasks on a task board grouped by column. - **List Tasks By Time** Returns tasks grouped by when they are due, which is the today, this week and overdue view. - **Get Task Card** Returns one task in its card shape, with the extras the board view shows. - **Add Subtask** Adds a subtask to a task. - **Update Subtask** Changes a subtask, for example to mark it done. - **Delete Subtask** Removes a subtask. - **List Task Comments** Returns the comments on a task. - **Add Task Comment** Comments on a task. - **Update Task Comment** Changes a task comment. A full replacement, so the whole comment is sent. - **Delete Task Comment** Deletes a task comment. - **Like Task Comment** Likes or unlikes a task comment as the token's own user. ### Activities 8 - **List Activities** Returns the logged activities: calls, meetings and whatever else the workspace defined as an activity type. - **Create Activity** Logs an activity against a record. - **Update Activity** Changes a logged activity. - **Delete Activity** Deletes a logged activity. - **List Activity Types** Returns the activity types the workspace defines, which is where Create Activity's type id comes from. - **Create Activity Type** Defines a new kind of activity. - **Update Activity Type** Changes an activity type. - **Delete Activity Type** Deletes an activity type. Activities already logged under it are affected, so a type in use is checked before removal. ### People and Departments 11 - **List Users** Returns the people in the workspace. - **Get User** Returns one workspace user. - **Create User** Adds a person to the workspace, which usually consumes a seat on the subscription. - **Update User** Changes a workspace user. - **Delete User** Removes a person from the workspace. What happens to the records they own depends on the workspace settings, so an owner is checked before removal. - **Get User Profile** Returns a user's profile settings and preferences. - **Update User Profile** Changes a user's profile settings. - **List Departments** Returns the workspace's departments. - **Create Department** Creates a department. - **Update Department** Changes a department. - **Delete Department** Deletes a department. The people in it survive. ### Account and Access 6 - **Get Account** Returns the workspace account with its name, plan and limits. - **Get Account Settings** Returns the workspace's settings. - **Update Account Settings** Changes the workspace's settings. A full replacement, so the whole settings object is sent. - **List Access Tokens** Returns the API tokens issued to the calling user, the same list the account settings screen shows. - **Create Access Token** Issues a new API token for the calling user. The token value is returned once and Amwork will not show it again, so it is stored immediately. - **Delete Access Token** Revokes an API token. If it is the token the connection uses, the connection stops working immediately. ### Email Templates 7 - **List Email Templates** Returns the workspace's email templates. - **Get Email Template** Returns one email template. - **Create Email Template** Creates an email template, carrying the merge fields List Template Placeholders reports. - **Update Email Template** Changes an email template. A full replacement, so the whole template is sent. - **Delete Email Template** Deletes an email template. - **Process Email Template** Renders a template against a record with its merge fields resolved, so a flow can see exactly what the recipient would before anything is sent. - **List Template Placeholders** Returns the merge fields an email template can carry. ### Mail 8 - **List Mailboxes** Returns the mailboxes connected to the workspace. - **List Mail Messages** Returns the messages in a mailbox. - **Get Mail Message** Returns one email message in full. - **Send Mail** Sends an email from a connected mailbox. This sends real mail from the workspace's own address. - **Mark Mail Thread** Marks a mail thread seen, unseen, spam, not spam, trashed or untrashed. - **Download Mail Attachment** Downloads an email attachment and stores it in FlowRunner file storage. - **Create Contact From Mail** Creates a CRM record from an email message, turning an unknown sender into a contact without copying the address by hand. - **List Signatures** Returns the email signatures in the workspace. ### Documents 3 - **List Document Templates** Returns the document templates the workspace can generate from. - **Create Document** Generates a document from a template and a record. - **List Entity Documents** Returns the documents generated against one record. ### Notifications 3 - **Get Unseen Notification Count** Returns how many notifications the calling user has not seen. Cheap enough to poll on a schedule. - **Mark Notification Seen** Marks one notification, or all of them, as seen. - **Get Notification Settings** Returns the calling user's notification preferences. ### File Storage 3 - **Upload File** Uploads a file to Amwork's storage and returns its id. Uploading only stores it; Add Entity Files is what attaches it to a record. - **Get File Info** Returns a stored file's metadata. - **Delete File** Deletes a stored file. It disappears from every record it was attached to. ### Automation 4 - **List Automation Processes** Returns the workspace's automation processes. - **Get Automation Process** Returns one automation process with its definition. - **Create Automation Process** Creates an automation process. The definition is Amwork's own process shape and passes through untouched. - **Delete Automation Process** Deletes an automation process. ### Reports 4 - **Get General Report** Returns the workspace's general CRM report. - **Get Pipeline Report** Returns a pipeline report for one entity type, with the filter traveling in the request body. - **Get Top Sellers** Returns the top performing people for an entity type. - **Get Summary Report** Returns a summary count for entities, tasks or activities on one entity type. ## Frequently Asked Questions ### What can FlowRunner do with Amwork? FlowRunner agents can run List Entity Types, Get Entity Type, and Create Entity Type in Amwork, plus 111 more actions. ### Does connecting Amwork to FlowRunner require OAuth? No. Amwork connects to FlowRunner with an API key, no OAuth flow required. ### Can Amwork trigger a FlowRunner workflow automatically? Amwork doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Amwork?** This integration exposes Amwork to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/amwork. Site index: https://flowrunner.ai/llms.txt