When using the Swordfish API or integrations (such as Zapier), you have the ability to set a “must_have” parameter. This allows you to control when credits are used, based on whether specific data points are found.
This is especially useful when you only want to pay for results that include certain contact details (like email or phone).
What Is the must_have
Setting?
The must_have
setting tells Swordfish which types of contact info must be present in the result in order to count the search as a match and deduct a credit.
Here’s how the values work:
Value | Requirement |
---|---|
1 | Any email |
2 | Any phone |
3 | Mobile phone only |
4 | Email OR any phone (default) |
5 | Email AND any phone |
6 | Email OR mobile phone |
7 | Email AND mobile phone |
Why It Matters
Let’s say you only want to collect mobile numbers and don’t want to be charged for results without one. You would set the must_have
value to 3
.
If you’re okay with getting either an email or phone, then stick with the default value of 4
.
Example Use Case in Zapier
In a Zapier automation where Swordfish is enriching new CRM contacts, you can use the must_have
value to:
Avoid wasting credits on partial results
Ensure your CRM only stores fully enriched contacts
Customize what qualifies as a “match” for your workflow
Where to Use It
You’ll encounter the must_have
setting when:
Creating Zaps with the Multiple Field Search action
Making API calls directly to the Swordfish platform
Uploading files for enrichment (advanced settings)
Need Help Choosing a Value?
If you're unsure which value to use for your use case, feel free to contact our team at [email protected]. We're happy to help you set up your integration for the best possible results.