SuiteDash
Project ManagementSuiteDash is the all-in-one client portal and business software with CRM, projects and marketing built in. Agents create and update contacts and companies, manage projects, subscribe audiences and read the attribute schemas that say what your own account accepts.
What This Integration Enables
Most connectors assume a schema. SuiteDash will not let you: it builds the contact, company and project field lists per account, including custom fields, circles and marketing audiences, and the three attribute operations exist because they are the only honest way to know what a write will accept. That shapes how an agent should behave here. It reads the schema, then it writes. It does not carry a field map from a sample account and hope.
The rest of the surface is deliberately narrow, and the boundaries are worth knowing before you design around them. Contacts and companies can be created and updated. Projects can be read and updated but not created, so a workflow has to start from a project that already exists. Idle companies are excluded from the listing entirely. Lookups accept an email address or a company name where most APIs demand an identifier, which removes a resolution call from every flow. Where it matters most, the connector reaches the client portal itself, and anything that touches a real client's inbox is where a human-in-the-loop step earns its place.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Onboarding an intake batch without mailing the whole list
New clients close in HubSpot or land as rows in Google Sheets. The agent starts with Get Contact Attributes, because the custom fields and audience identifiers it needs are particular to this account, then maps the incoming columns onto names the account will accept and puts anything unmatched through the general fields path. Get Contact resolves each person by email address, so there is no separate lookup. Existing people are refreshed with Update Contact. New people are created with Create Contact, and here the agent deliberately does not decide: it leaves the welcome email off, records who would have been invited, and hands that list to a person.
-
Company records that stay pointed at a real contact
A company in SuiteDash needs a primary contact by email address, and Create Company will either find that address or create the person, depending on how the call is shaped. The agent reads Get Company Attributes first, because a company carries three separate custom field sets and only the account knows which is which. It then resolves the company by name with Get Company, refreshes it with Update Company, and creates it only when nothing matches. Because idle companies are absent from the listing, the agent treats a missing row as unknown rather than as absent, and confirms with a direct lookup before creating a duplicate.
-
Keeping the portal current without polling it
SuiteDash meters API calls by plan, and a listing hands back ten rows a page with no way to ask for more, so a workflow that polls the account will burn its allowance and answer with a forbidden response instead of data. The agent is built the other way around: it reacts to events elsewhere. A signed document in DocuSign or a payment in Stripe triggers a targeted Get Project and Update Project against the one project involved, and a digest goes to Slack. List Projects and List Contacts are used for reconciliation on a slow schedule, not as a change feed.
Human-in-Loop Highlight
The costly operation in SuiteDash is not a delete, because the API does not offer one. It is a single field on Create Contact called Send Welcome Email. Leave it on during an import and every person in the batch is invited into the client portal by email, at once, from a workflow that was meant to be tidying records. There is no recall, and the first sign anything went wrong is a client asking why they were invited to a portal they already use. Subscribe To Marketing has the same shape: it adds people to audiences, and consent is not something an agent should infer from a spreadsheet column. So the import agent writes the records with invitations off, then stops and asks in the onboarding channel: "38 contacts created. 12 are new people with no portal access. Invite all 12, invite only the 4 named as primary contacts, or invite none? Two of the 38 carry a marketing opt-in flag from the source. Subscribe those two to the newsletter audience?" The records are already correct. What waits is the part that reaches a client.
Agent Capabilities
16 actionsContacts
5- List Contacts Returns the CRM contacts. A page holds ten rows and the size cannot be raised, so a workflow reading everything walks the pages deliberately rather than by accident.
- Get Contact Returns one contact, addressed by either its identifier or its email address. A workflow holding only an address does not need a lookup first.
- Create Contact Adds a CRM contact. An email address is required for every role except lead, and the welcome email setting decides whether the person is invited into the portal.
- Update Contact Changes a contact. Which fields an account accepts is per account, so the attribute schema is what tells the truth and anything unnamed goes through the general fields path.
- Get Contact Attributes Returns the complete contact schema for this account, including custom fields, circles and marketing audiences. The first call in any write workflow.
Companies
5- List Companies Returns the CRM companies. Idle companies are not returned at all, so a missing row means unknown rather than absent.
- Get Company Returns one company, addressed by either its identifier or its name.
- Create Company Creates a CRM company. A company needs a primary contact by email address, and a setting decides whether SuiteDash creates that person when the address is unknown.
- Update Company Changes a company. A company carries three separate custom field sets, public, private and target, and only the account's own schema says which is which.
- Get Company Attributes Returns the complete company schema for this account, including all three custom field sets.
Projects
4- List Projects Returns the account's projects.
- Get Project Returns one project, looked up by identifier, by exact name, by a fragment of the name, or as the most recent one.
- Update Project Changes a project. There is no route to create one, so a workflow has to start from a project that already exists.
- Get Project Attributes Returns the complete project schema for this account, which is where the real update field list comes from.
Marketing and Worlds
2- Subscribe To Marketing Subscribes people to marketing audiences, several at once. Audience identifiers are particular to the account and come from the contact attribute schema.
- List Worlds Returns the account's Worlds, the separately branded portals a contact or company can belong to. It requires the Worlds power-up and says so plainly when it is not active.
Frequently Asked Questions
What can FlowRunner do with SuiteDash?
FlowRunner agents can run List Contacts, Get Contact, and Create Contact in SuiteDash, plus 13 more actions.
Does connecting SuiteDash to FlowRunner require OAuth?
No. SuiteDash connects to FlowRunner with an API key, no OAuth flow required.
Can SuiteDash trigger a FlowRunner workflow automatically?
SuiteDash doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Project Management integrations
Start building with SuiteDash
Free plan, no card required. Connect in minutes.