Formilla

@Formilla create a contact for sarah.chen@example.com with name Sarah Chen and tag her as enterprise-trial

Contact upserted successfully in Formilla. Because the tool matches by user ID first (none provided here) then email, this either created a new contact record for sarah.chen@example.com or updated an existing one with the name and tag you specified. The API does not return the contact ID or confirm whether this was a create or update operation, so you won't see a record link or confirmation of which fields changed.

This example shows the core upsert workflow. The MCP does not return contact data or IDs after the operation, so you cannot immediately verify what changed or link to the record in Formilla's UI. Useful for bulk contact syncs where confirmation isn't required, but less ideal if you need to chain operations or audit the result.

@Formilla update the contact with user ID abc-123 to set their company to Acme Corp and add a note that they requested a demo on 2025-01-15

Contact upserted in Formilla using user ID abc-123 as the match key. The company field and note were written to the contact record. If no contact existed with that user ID, a new one was created. Because the tool returns no data, you won't see which fields were overwritten or whether this was a new contact versus an update to an existing one.

User ID takes precedence over email when matching, so this example targets a specific contact by its internal identifier. The lack of return data means you cannot confirm the operation's effect without a separate lookup in Formilla's dashboard. Best for workflows where you trust the match logic and don't need immediate feedback.

@Formilla take the five leads from the last Slack thread and upsert them into Formilla with tag 'q1-webinar-attendees' and source 'slack-discussion'

I've extracted five email addresses and names from the Slack thread context and upserted each as a Formilla contact with the tag 'q1-webinar-attendees' and custom field 'source' set to 'slack-discussion'. Each upsert succeeded, but the tool does not return contact IDs or confirm whether these were new records or updates to existing ones. You'll need to check Formilla's contact list to verify the batch import.

This synthesis example pairs the MCP with AI reasoning to bulk-import leads from unstructured conversation data. The lack of return data makes it harder to audit the batch operation or catch partial failures. Requires an API key with contact-write scope. Useful for quick imports where manual verification is acceptable.

When webinar signups need instant chat follow-up prep

A 2-person marketing team runs monthly webinars and wants every registrant in Formilla before the event starts, tagged with their signup questions. The Formilla MCP handles this batch-style enrichment: after registration closes, Switchy loops through the signup sheet and upserts each contact with webinar-specific fields. The MCP's match-by-email logic means repeat attendees get updated, not duplicated. The catch: with only one tool and no read capability, you can't check if a contact already exists or pull their chat history before upserting. If your workflow depends on conditional logic—like 'only upsert if this is their first event'—you'll hit a wall. But if you're pushing net-new or refresh data into Formilla and don't need the response payload, this MCP keeps your contact list current without a Zapier tax.