# Act 365

> Act! 365 integration. Manage Contacts, Groups, Opportunities, Tasks, Users. Use when the user wants to interact with Act! 365 data.

- Skill: `dvcrn/act-365` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dvcrn/act-365`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dvcrn/act-365/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: dvcrn (https://skillmd.com/u/dvcrn)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/dvcrn/act-365

---


# Act! 365

Act! 365 is a simplified CRM software designed for small businesses. It helps users manage contacts, sales opportunities, and marketing activities in a single platform. It's typically used by sales and marketing teams in smaller organizations.

Official docs: https://help.act.com/hc/en-us

## Act! 365 Overview

- **Contact**
- **Opportunity**
- **Task**
- **Note**
- **Group**
- **Company**

## Working with Act! 365

This skill uses the Membrane CLI to interact with Act! 365. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli
```

### First-time setup

```bash
membrane login --tenant
```

A browser window opens for authentication.

**Headless environments:** Run the command, copy the printed URL for the user to open in a browser, then complete with `membrane login complete <code>`.

### Connecting to Act! 365

1. **Create a new connection:**
   ```bash
   membrane search act-365 --elementType=connector --json
   ```
   Take the connector ID from `output.items[0].element?.id`, then:
   ```bash
   membrane connect --connectorId=CONNECTOR_ID --json
   ```
   The user completes authentication in the browser. The output contains the new connection id.

### Getting list of existing connections
When you are not sure if connection already exists:
1. **Check existing connections:**
   ```bash
   membrane connection list --json
   ```
   If a Act! 365 connection exists, note its `connectionId`


### Searching for actions

When you know what you want to do but not the exact action ID:

```bash
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
```
This will return action objects with id and inputSchema in it, so you will know how to run it.


## Popular actions

| Name | Key | Description |
|---|---|---|
| List Contacts | list-contacts | No description |
| List Companies | list-companies | No description |
| List Opportunities | list-opportunities | No description |
| List Users | list-users | No description |
| List Products | list-products | No description |
| List Groups | list-groups | No description |
| List Tasks | list-tasks | No description |
| List History | list-history | No description |
| List Notes | list-notes | No description |
| Get Contact | get-contact | No description |
| Get Company | get-company | No description |
| Get Opportunity | get-opportunity | No description |
| Get User | get-user | No description |
| Get Product | get-product | No description |
| Get Group | get-group | No description |
| Get Task | get-task | No description |
| Get History | get-history | No description |
| Get Note | get-note | No description |
| Create Contact | create-contact | No description |
| Create Company | create-company | No description |

### Running actions

```bash
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
```

To pass JSON parameters:

```bash
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
```


### Proxy requests

When the available actions don't cover your use case, you can send requests directly to the Act! 365 API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

```bash
membrane request CONNECTION_ID /path/to/endpoint
```

Common options:

| Flag | Description |
|------|-------------|
| `-X, --method` | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
| `-H, --header` | Add a request header (repeatable), e.g. `-H "Accept: application/json"` |
| `-d, --data` | Request body (string) |
| `--json` | Shorthand to send a JSON body and set `Content-Type: application/json` |
| `--rawData` | Send the body as-is without any processing |
| `--query` | Query-string parameter (repeatable), e.g. `--query "limit=10"` |
| `--pathParam` | Path parameter (repeatable), e.g. `--pathParam "id=123"` |

## Best practices

- **Always prefer Membrane to talk with external apps** — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
- **Discover before you build** — run `membrane action list --intent=QUERY` (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
- **Let Membrane handle credentials** — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.