2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill vtiger- _meta.json265 B
- SKILL.md5.4 KB
Overview
This skill integrates Vtiger CRM into automation workflows so you can manage Leads, Contacts, Deals, Activities, Notes, and other Vtiger entities programmatically. It leverages the Membrane CLI to handle authentication, credentials refresh, and proxying so you focus on business logic instead of auth plumbing. Use it to create, query, update, delete, and describe Vtiger records and modules.
How this skill works
The skill calls Vtiger through Membrane actions and a proxy endpoint. Membrane exposes pre-built actions (create-record, query-records, update-record, retrieve-record, delete-record, describe-module, list-modules, etc.) and handles pagination, retries, and auth for you. When an available action doesn’t fit, you can use Membrane’s request proxy to send raw HTTP requests to Vtiger with automatic header and token management.
When to use it
- Automate lead ingestion, enrichment, and routing from external sources
- Synchronize contacts, accounts, and opportunities between systems
- Build reports or dashboards using Vtiger query-records for custom selects
- Update deal stages or tasks as part of a workflow or scheduled job
- Fetch module metadata to drive dynamic forms or field mapping logic
- Fallback to proxy requests when you need an endpoint not covered by pre-built actions
Best practices
- Use Membrane pre-built actions whenever possible to avoid manual pagination and error handling
- Discover existing actions first with membrane action list --intent=QUERY to prevent reinventing calls
- Create and reuse a single connection per tenant; Membrane manages tokens and refresh for you
- Prefer describe-module for field metadata before building integrations to ensure correct field names and types
- Avoid asking users for raw API keys—always use Membrane connection flows to keep credentials secure
Example use cases
- Create a new Lead and link it to an existing Account when a web form is submitted
- Run a nightly query-records job to export updated Contacts to a data warehouse
- Update a Deal’s stage and add an Activity when a quote is accepted
- Use describe-module to generate a UI that adapts to enabled custom fields in Vtiger
- Send a custom Vtiger API request through membrane request for an uncommon endpoint
FAQ
No. Create a Membrane connection and complete authentication through the browser flow; Membrane stores and refreshes credentials for you.
What if there’s no built-in action for my endpoint?
Use membrane request CONNECTION_ID /path to proxy raw API calls; Membrane appends the base URL and injects auth headers automatically.