finta-rate-limits
Understand Finta usage limits and plan tiers. Trigger with phrases like "finta limits", "finta plan limits".
What this skill does
# Finta Rate Limits
## Overview
Finta operates as a web-first fundraising platform without a traditional REST API, so rate limits manifest as plan-tier usage caps rather than HTTP request quotas. When building integrations through Finta's webhook events or Zapier connectors, the bottleneck is typically the number of investor pipeline records, deal room operations, and Aurora AI suggestion calls you can make within your plan tier. Teams running active fundraising rounds need to understand these ceilings to avoid mid-raise disruptions.
## Rate Limit Reference
| Endpoint / Feature | Limit | Window | Scope |
|---------------------|-------|--------|-------|
| Investor pipeline records | 50 (Free) / Unlimited (Pro) | Rolling | Per workspace |
| Deal room creation | 1 (Free) / Unlimited (Pro) | Rolling | Per workspace |
| Aurora AI suggestions | 10/day (Free) / 100/day (Pro) | 24 hours | Per user |
| Webhook event delivery | 100 events | 1 minute | Per workspace |
| Data room file uploads | 25 (Free) / Unlimited (Pro) | Rolling | Per deal room |
## Rate Limiter Implementation
```typescript
class FintaUsageTracker {
private counts: Map<string, { used: number; limit: number; resetAt: number }> = new Map();
register(resource: string, limit: number, windowMs: number) {
this.counts.set(resource, { used: 0, limit, resetAt: Date.now() + windowMs });
}
async acquire(resource: string): Promise<boolean> {
const entry = this.counts.get(resource);
if (!entry) throw new Error(`Unknown resource: ${resource}`);
if (Date.now() > entry.resetAt) { entry.used = 0; entry.resetAt = Date.now() + 86_400_000; }
if (entry.used >= entry.limit) return false;
entry.used++;
return true;
}
remaining(resource: string): number {
const entry = this.counts.get(resource);
return entry ? entry.limit - entry.used : 0;
}
}
const tracker = new FintaUsageTracker();
tracker.register("aurora_suggestions", 100, 86_400_000);
tracker.register("webhook_events", 100, 60_000);
```
## Retry Strategy
```typescript
async function fintaWebhookRetry(payload: any, webhookUrl: string, maxRetries = 3): Promise<void> {
for (let attempt = 0; attempt <= maxRetries; attempt++) {
try {
const res = await fetch(webhookUrl, {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify(payload),
});
if (res.ok) return;
if (res.status === 429) {
const delay = Math.pow(2, attempt) * 5000 + Math.random() * 2000;
await new Promise(r => setTimeout(r, delay));
continue;
}
throw new Error(`Webhook delivery failed: ${res.status}`);
} catch (err) {
if (attempt === maxRetries) throw err;
await new Promise(r => setTimeout(r, Math.pow(2, attempt) * 3000));
}
}
}
```
## Batch Processing
```typescript
async function batchSyncInvestors(investors: any[], batchSize = 20) {
const results: any[] = [];
for (let i = 0; i < investors.length; i += batchSize) {
const batch = investors.slice(i, i + batchSize);
for (const investor of batch) {
const allowed = await tracker.acquire("webhook_events");
if (!allowed) { await new Promise(r => setTimeout(r, 60_000)); }
results.push(await fintaWebhookRetry(investor, WEBHOOK_URL));
}
if (i + batchSize < investors.length) await new Promise(r => setTimeout(r, 3000));
}
return results;
}
```
## Error Handling
| Issue | Cause | Fix |
|-------|-------|-----|
| Plan limit reached | Free tier investor cap (50) | Upgrade to Pro or archive inactive investors |
| Aurora AI unavailable | Daily suggestion quota exhausted | Wait for 24h reset or upgrade plan |
| Webhook delivery 429 | Burst of pipeline events | Queue events, deliver with 1s spacing |
| Deal room locked | Free plan single-room limit | Close existing room before opening new one |
| File upload rejected | Data room storage cap on Free tier | Compress files or upgrade plan |
## Resources
- [Finta Pricing](https://www.trustfinta.com/pricing)
## Next Steps
See `finta-performance-tuning`.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.